Hi Carlos, This is similar to Daniel's issue. Are you setting the ignoreAttributes to true or false in the registry entry?
--- *John Gasper* IAM Consultant Unicon, Inc. PGP/GPG Key: 0xbafee3ef On 10/9/14 12:31 PM, Carlos Olivera wrote: > Hi everyone, I'm currently working with Cas server 4.0 and applying > customizations, but there's still something I can't quite figure out yet. > > In the section of attribute release says: > > First: > Attributes are controlled by the Person Directory project and returned to > scoped services via the SAML 1.1 protocolor the CAS protocol. > Attributes pass through a two-step process: > > Resolution: Done at the time of establishing the principal via > PrincipalResolver components where attributes are resolved from various > sources that are outlined below. > Release: Adopters must explicitly configure attribute release for services in > order for the resolved attributes to be released to a service in the > validation response. > My question is, what happens when the service reduces the number of > attributes to release either by using "getAllowedAttributes" or by > getAttributeFilter? Does it mean that whenever I get a reference to > AttributePrincipal in the client, only those released attributes will be > available? If I'm getting that last one wrong, what is the use of > allowedAttributes? > > In my current implementation, I always receive all the attributes (via SAML) > in the client no matter how many filters I set up. > > Thanks in advance and sorry for my English ;) -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
