[Building Sakai] AuthenticatedUserProvider - EID in CM differs from login

[Ray Davis]

Your use case is pretty much exactly what the AuthenticatedUserProvider 
was meant to cover. (At UC Berkeley, we use a non-private but 
not-used-by-real-people UID to identify externally authenticated 
students and instructors, but they log in by using a completely 
different ID with stricter privacy rules.)

Here's the related JIRA page:

http://jira.sakaiproject.org/jira/browse/SAK-9854

And here's how we use the new interface locally:

https://source.sakaiproject.org/contrib/ucb/ucb-integration-samples/bspace-user-provider-impl

In particular, see:

https://source.sakaiproject.org/contrib/ucb/ucb-integration-samples/bspace-user-provider-impl/src/main/java/edu/berkeley/bspace/UserDirectoryProviderBspaceImpl.java

Best,
Ray

On 5/19/2009 10:13 AM, Stephen Jaegle wrote:
> Hi all:
> 
> Our SIS references nine digit id numbers rather than login tokens such as
> jsmith, but we would like to have our users login with their customary login
> tokens.
> 
> I notice that  BaseUserDirectoryService.getProviderAuthenticatedUser will
> use a provider that is an instance of AuthenticatedUserProvider. The
> available LDAP contains references to both the login token and the nine
> digit id. My current thinking is to create a class that implements
> AuthenticatedUserProvider, authenticates the user and returns a UserEdit
> object with the nine digit id set as the EID. Does anyone know whether this
> approach will be sufficient to allow users to log in with a token other than
> the EID stored in SAKAI_USER_ID_MAP.EID? Are their other areas that will
> need changes?
> 
> Thanks,
> 
> Steve
>