I actually figured it out. I did not configure the allowable attributes with
the InMemoryServiceRegistryDaoImpl. Once I did that, I was able to have the
attributes displayed.
However, now that I have them displayed, I cannot get the attributes out on the
client side. I'm using the CAS20ProxyTicketValidator - not sure if this is the
right one to get the extra information I need - but it appears as if the
attributes that I created are in the wrong format. When I use the
casServiceVlaidationSuccess.jsp it puts out attributes in the following format:
<cas:attributes>
<cas:attribute>
<cas:name>myAttributeName</cas:name>
<cas:value>myAttributeValue</cas:value>
</cas:attribute>
</cas:attributes>
When the proxy ticket validator iterates through the attributes, it puts
"name", "value" into the principal's attributes instead of "myAttributeName"
and "myAttributeValue" into the attributes.
So should I even be using the CAS20ProxyTicketValidator or use the Saml
validator? Going to the saml validator would cause a huge upheaval and I'm not
comfortable doing that at this point - we might migrate later. So I'm going to
try and alter the jsp so that the client will understand the attributes, namely:
<cas:myAttributeName>myAttributeName</cas:myAttributeName>
<cas:myAttributeValue>myAttributeValue</cas:myAttributeValue>
I'm just unsure if this is even the right approach.
Thanks in advance for your assistance.
Russ Baker
--
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
