Geolocation attribute

[O'Dowd, Josh]

Maybe you extend the password-authn-flow[1], and have the user select their portal location as an extension option.

-Josh

[1} https://wiki.shibboleth.net/confluence/display/IDP30/PasswordAuthnConfiguration#PasswordAuthnConfiguration-CallingExtendedFlows3.2
________________________________________
From: users [users-bounces at shibboleth.net] on behalf of Yavor Yanakiev [yavor at nyu.edu]
Sent: Friday, April 21, 2017 8:39 AM
To: Cantor, Scott
Cc: idm.services at nyu.edu; Shib Users; Scott Koranda; Scott Koranda
Subject: Re: Geolocation attribute

Yes, it is all about licensing in the Apporto case.
We have to find a way to apply proper license, based on which country the principal is situated at the moment.
Another use-case, which applies to NYU, is to automatically provide supplemental login/help information in a language based on the user's location.

On Fri, Apr 21, 2017 at 9:45 AM, Cantor, Scott <cantor.2 at osu.edu<mailto:cantor.2 at osu.edu>> wrote:
> We just started a pilot use of http://apporto.com and since the software
> licenses can be different in each country, we need to know where the
> particular user is.

Perhaps this isn't really about geolocation at all then, it's about licensing. If the vendor wants a license code assigned to the login, that's a different problem.

Sort of like when vendors ask for your "organization ID" when what they really want is their billing ID.

Just another way to look at it.

-- Scott




--
Yavor Yanakiev
Systems Developer for Identity Services
212-992-7585