Hello everyone,
I know this topic has been covered fairly many times but I could not come to
a conclusion with the information available, so need your help here.
Use case is simple - I would like to fetch some attributes in response after
the user has been successfully authenticated. These attributes could either
be dynamic (dao fetch) or static (hardcoded). I'm using CAS 3.3.4.
My questions -
1. I have two authentication handlers. Can I configure two sets of
attributes responses as well (as determined by which handler authenticated
the request)? *Need help here please!*
2. I understand that there are few ways to send attributes in response -
2.1 The somewhat correct way (pre 3.3.2?): In *
casServiceValidationSuccess.jsp*, just after the <cas:user> end tag, put
down the attributes. There's some confusion here - the format of the
attribute tags. There are at least 3 different versions floating around. My
question is which one is the standard? Or does anything goes as far as
client can handle it?
(a)
<cas:attributes>
<cas:attribute>
<cas:name>${fn:escapeXml(attr.key)}</cas:name>
<cas:value>${fn:escapeXml(attr.value)}</cas:value>
</cas:attribute>
</cas:attributes>
(b) <cas:attribute name="attr.key" value="attr.value"/>
(c)
<cas:attributes>
<cas:{attr.key}>attr.value</cas:{attr.key}>
</cas:attributes>
2.2 The correct way: In *deployerConfigContext.xml* using *
attributeRepository*. We have
https://wiki.jasig.org/display/CASUM/Attributes for reference. Instead of
LDAP, how about a DAO example or even simpler static (hardcoded) values in
response? Is there a need for a Resolver? *Need to understand this*.
Thanks!
--
RJ
--
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
