Hello everyone, I recently asked about returning attributes from a mainframe authentication. Luckily, things have been simplified since then :) We're now authenticating against a database, but I would still like to return one extra attribute from the database, but it maybe over-complicating things.
Here's the situation: both CAS and the app have access to the same user table in the DB. The user logs on, and the principle is returned to the app, which then loads extra info from the DB using the principle as the key. All works fine. However, I would like also to return the key of the row - i.e. the integer key. The app can use this instead as the 'where' clause to load the user. The reasoning behind this is that we might have to do case conversions etc. to initially authenticate the user, and this could get a bit complicated with the various character sets we want to support. Doing it in just one place - on the CAS side - makes sense, and if the app uses the integer value, it won't have to worry about all that. I'm using CAS 3.4.5 at present, and I'd rather not have to use the person directory stuff. I understans I need to use SAML etc., but what I can't find is how to simply return one extra attribute. Any advice would be gratefully received - including if you think this is not a good idea :) Many thanks, John -- 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
