I tried to debug the code in order to figure out when the principal was saved with all the attributes. I got the following Assertion (ImmutableAssertion) object created (ServiceValidateController):
- primaryAuthentication (ImmutableAuthentication): The Principal has an empty list of attributes, wich is what I need according to my configuation. - chainedAuthentications (List<ImmutableAuthentication>): Return a list with only one item, but in that case the Principal in the Authentication object has ALL the attributes of the user. Is that the standard behaviour in the login proccess? Something I haven't said yet, to retrieve the attributes from the client I use the following code: AttributePrincipal principal = (AttributePrincipal)request. Map attributes = principal.getAttributes(); is that ok??? I don't know if any of that helps, but maybe for an experienced user it could mean something. El lunes, 13 de octubre de 2014 08:51:15 UTC-2, [email protected] escribió: > > Hi, > > Here my deployerconfig. I have the same problem than carlos. I dont > understand why i have all attributes.. > I have tried both with Attributefilter and allowedattributes but its the > same. > > -- > You are currently subscribed to [email protected] <javascript:> as: > [email protected] <javascript:> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- 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
