principalIdAttribute truncation or modification?

[Patrick Gardella]

We are trying to find a middle ground between sAMAccountName and userPrincipalName to return via the principalIdAttribute in the ldapAuthenticationHandler bean. (We are using Active Directory to handle authentication.) For instance, the userPrincipalName is danny.armstron...@example.com and the sAMAccountName would be danny.armstrong.test  We instead want it to return danny.armstrong.testing123456. 

For the moment, we've started to use "uid" in Active Directory to be that truncated userPrincipalName, but I'd rather not, if possible have to use this long term.

Does anyone know a way to accomplish this?

Patrick

Asbury Seminary

[Patrick Gardella]

A different way of putting the question would be:

Is there a way to modify any return attribute from the LDAP attributes, besides to merge, replace, and/or add of MergingPersonAttributeDaoImpl? Without customizing the code, that is.

Patrick

On Friday, October 7, 2016 at 7:43:47 PM UTC-4, Patrick Gardella wrote:

We are trying to find a middle ground between sAMAccountName and userPrincipalName to return via the principalIdAttribute in the ldapAuthenticationHandler bean. (We are using Active Directory to handle authentication.) For instance, the userPrincipalName is danny.armstrong.testing123456@example.com and the sAMAccountName would be danny.armstrong.test  We instead want it to return danny.armstrong.testing123456. 

[Misagh Moayyed]

You don’t mention what CAS version; so I am going to say no unless you write something in Groovy. 

-- 
Misagh

--
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 cas-user+u...@apereo.org.
To post to this group, send email to cas-...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/1b3ad36a-1d5c-4d25-8b21-0f316bda773e%40apereo.org.
For more options, visit https://groups.google.com/a/apereo.org/d/optout.

[Patrick Gardella]

Sorry.  4.2.6.  And that was the conclusion I reached over the weekend.

Patrick

On Monday, October 10, 2016 at 4:13:54 AM UTC-4, Misagh Moayyed wrote:

You don’t mention what CAS version; so I am going to say no unless you write something in Groovy. 

-- 
Misagh

From: 'Patrick Gardella' via CAS Community <cas...@apereo.org>
Reply: Patrick Gardella <patrick...@asburyseminary.edu>
Date: October 8, 2016 at 10:49:18 PM
To: CAS Community <cas...@apereo.org>
Subject:  [cas-user] Re: principalIdAttribute truncation or modification?

A different way of putting the question would be:

Is there a way to modify any return attribute from the LDAP attributes, besides to merge, replace, and/or add of MergingPersonAttributeDaoImpl? Without customizing the code, that is.

Patrick

On Friday, October 7, 2016 at 7:43:47 PM UTC-4, Patrick Gardella wrote:

We are trying to find a middle ground between sAMAccountName and userPrincipalName to return via the principalIdAttribute in the ldapAuthenticationHandler bean. (We are using Active Directory to handle authentication.) For instance, the userPrincipalName is danny.armstron...@example.com and the sAMAccountName would be danny.armstrong.test  We instead want it to return danny.armstrong.testing123456. 

For the moment, we've started to use "uid" in Active Directory to be that truncated userPrincipalName, but I'd rather not, if possible have to use this long term.

Does anyone know a way to accomplish this?

Patrick

Asbury Seminary