Correct - i.e. CAS server implementation of CAS protocol v2 does not provide 
support for principal attributes.

Cheers,
D.


From: David Huebner <[email protected]>
Reply: David Huebner <[email protected]>
Date: June 30, 2017 at 8:40:05 AM
To: Dmitriy Kopylenko <[email protected]>, [email protected] 
<[email protected]>
Subject:  Re: [cas-user] Release Attributes from LDAP Authentication  

Thanks you.
When requesting with CAS protocol version 3 it does indeed work.
I was under the impression, that version 2 already supports attribute release, 
since the Shibboleth CAS support states, that it does support CAS v2 and it 
does attribute release.
So I kind of just assumed that this is part of v2, but I guess Shibboleth does 
some non-standard stuff there.


On 30.06.2017 14:33, Dmitriy Kopylenko wrote:
If your client is using CAS protocol version 2 for service ticket validation, 
they will not receive any attributes as protocol v2 does not support it. Switch 
to protocol version 3 in order to receive principal attributes.

https://apereo.github.io/cas/5.1.x/protocol/CAS-Protocol.html

Cheers,
D.




From: D. H. <[email protected]>
Reply: [email protected] <[email protected]>
Date: June 30, 2017 at 7:25:29 AM
To: CAS Community <[email protected]>
Subject:  [cas-user] Release Attributes from LDAP Authentication

Hi,

I want to configure CAS 5.1 to release some attributes from the LDAP 
authentication source.
This is an excerpt from my cas.properties with the relevant properties I 
configured:

cas.authn.ldap[0].enhanceWithEntryResolver=true
cas.authn.ldap[0].dnFormat=uid=%s,ou=people,dc=example,dc=org
cas.authn.ldap[0].principalAttributeId=uid
cas.authn.ldap[0].principalAttributeList=cn,sn

cas.authn.attributeRepository.defaultAttributesToRelease=cn,sn,mail

According to the log file, these rules do apply:

2017-06-30 13:19:24,517 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
<Default attributes for release are: [[cn, sn, mail]]>
2017-06-30 13:19:24,517 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
<Found and added default attribute for release: [cn]>
2017-06-30 13:19:24,517 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
<Found and added default attribute for release: [sn]>
2017-06-30 13:19:24,518 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
<Default attributes found to be released are [{cn=Test Benutzer, sn=Benutzer}]>
2017-06-30 13:19:24,518 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
<Adding default attributes first to the released set of attributes>
2017-06-30 13:19:24,518 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
<Adding policy attributes to the released set of attributes>
2017-06-30 13:19:24,518 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
<Final collection of attributes allowed are: [{cn=Test Benutzer, 
LdapAuthenticationHandler.test.benutzer=uid=test.benutzer,ou=people,dc=example,dc=org,
 sn=Benutzer}]>
2017-06-30 13:19:24,518 DEBUG 
[org.apereo.cas.services.DefaultRegisteredServiceUsernameProvider] - <Returning 
the default principal id [test.benutzer] for username.>

However, here is what my client receives:

Response Body:  
4323 .|    |    |    |    |    |    <cas:serviceResponse 
xmlns:cas='http://www.yale.edu/tp/cas'>
4323 .|    |    |    |    |    |        <cas:authenticationSuccess>
4323 .|    |    |    |    |    |            <cas:user>test.benutzer</cas:user>
4323 .|    |    |    |    |    |            </cas:authenticationSuccess>
4323 .|    |    |    |    |    |    </cas:serviceResponse>

So, no attributes. Clearly I am missing something, I just can not seem to 
figure out what.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/65d0e38c-d4ec-410e-b47d-0be81d52f9b2%40apereo.org.


 

This email has been scanned for spam and viruses by Proofpoint Essentials. 
Click here to report this email as spam.


-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/etPan.59564935.541aa082.221%40unicon.net.

Reply via email to