thanks Andrew, you just safe my life, Please notify me when you upload your solution to your GitHub account, meanwhile I´ll take a look of the information that you just share with me. Thanks again.
Cheers 2012/2/2 Andrew Petro <[email protected]> > Yes. Very possible. Functionality I'm intending to contribute for 3.5. > > I'll create a branch in my GitHub account and share my solution for this, > and then I'll appreciate your taking a look / locally validating it meets > the need / improving. > > Feature targeted for CAS 3.5 documented here: > > > https://wiki.jasig.org/display/CAS/CAS+Services+Registry+Improvements+for+CAS+3.5#CASServicesRegistryImprovementsforCAS35-Per-serviceselectionofwhichuserattributetotreatastheusernameintheCASprotocol > > Long past time to get that one done. > > Andrew > > > On Feb 1, 2012, at 5:51 PM, Oliver Forlan Gutierrez wrote: > > > Hi Andrew: > > > > First of all thanks for your answer, I was thinking to add > this attribute to the ldap where CAS log on, for example: > > > > User: X, App1User: Y, App2User: Z > > User: X1, App1User: Y1, App2User Z1 > > > > The idea is that the user always log with the same user in > this case X or X1, and depending on the app that makes the request return > the corresponding attribute, Is this possible? > > > > Cheers. > > > > 2012/2/1 Andrew Petro <[email protected]> > > 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 > > > > > > -- > > 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 > > -- 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
