Oliver, Do you have, I hope, a mapping table or source of attributes such that the correct username for each participating application for a given unified principal (user) is known to CAS?
That is, can CAS *know* that you're X in App1, Y in App2, and Z in App3? If so, then you model all those alternative usernames as user attributes, enhance the service registry to model the metadata of which attribute to use as the username for each service, and viola! CAS uses the correct, expected username for the user in each service. I'm sitting on a customization that does just that, actually. Really need to get that released publicly and, when all goes well, merged for inclusion in 3.5. It's on the roadmap and I showed it a bit at the UnConference. If you don't have these mappings available so that CAS can't know the right username to use in each service, well, then I'm not sure what you do. Andrew On Feb 1, 2012, at 2:40 PM, Oliver Forlan Gutierrez wrote: > Hi every one. > > > I´m implementing CAS on different applications, one’s are > developed in php, others in JSP, etc, everything is working fine, but all > applications have different users, I mean App1 my user is X, App2 my user is > Y, App3 my user is Z, how do you solve this problem until you unify the users > names, we are talking about applications with more than 10,000 users. > > > Cheers. > > > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
