Marvin and Scott,
Thanks for taking time to answer my questions. I went back and spent some
time thinking about what it is that I am trying to do and clarify my problem
statement(s).
Starting with the use case( feel free to tell me this is an absolutely
ridiculous thing to do):
1) User logs in to CASified app.
2) Upon successful authentication, CAS retrieves the mapped attributes and
populates the user principal
3) CAS redirects to the app
4) The application can then retrieve the principal and through the
principal, retrieve the attributes that
CAS retrieved for the user on login.
This is what sent me down the CredentialsToLDAPAttributePrincipalResolver
path.
I configured them, for both our attributeSources(ActiveDirectory and Novell)
and you know the rest.
Taking a step back I removed ActiveDirectory and tried again. I see CAS
find the user and retrieve the attributes I mapped in the config file and
populate the LdapPersonAttributeDao. On redirect to my CASified app I do not
see the attributes in the principal, they are empty. Is my assumption
correct in that CAS will populate the principal with the retrieved
attributes?
Once I get this working, I can work on the PartialResultsException
Thanks again
Dean
--
View this message in context:
http://jasig.275507.n4.nabble.com/CredentialsToLDAPAttributePrincipalResolver-principal-attributes-revisited-tp2224907p2224907.html
Sent from the CAS Users mailing list archive at Nabble.com.
--
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
