With the default configuration of the serviceRegistryDao I selected the "Ignore
Attribute Management via this Tool" checkbox for all services... and... it
doesn't change anything to my problem. :/
Here is my attribute repository:
<bean id="attributeRepository"
class="org.jasig.services.persondir.support.StubPersonAttributeDao">
<property name="backingMap">
<map>
<entry key="uid" value="uid" />
<entry key="eduPersonAffiliation" value="eduPersonAffiliation" />
<entry key="groupMembership" value="groupMembership" />
</map></property></bean>
Here is the end of my method resolvePrincipal:
convertedAttributes.put("uid", "uid");
return new UtilisateurConnectePrincipal(principalId, convertedAttributes);
UtilisateurConnectePrincipal is a self-made Principal that I made from
SimplePrincipal with a modifiable map... I tried SimplePrincipal too and result
is the same...
I add the couple (uid,uid) because before I did the map was empty (I thought the
backingMap should intervene, but... visibly not). When the Principal is created
the attributes are well transmitted... But after they are created, they
disappears in the Warp. :x
Selon Marvin Addison <[email protected]>:
> > Connection is well-made, the principal is created with the attributes I
> gave him... And... and what? Is it enough? ... in both cases I can't reach
> the Principal with my client applications.
>
> You need to ensure the service is authorized to receive the attributes
> in the service manager component. See the yellow note on
> https://wiki.jasig.org/display/CASUM/Attributes.
>
> M
>
> --
> 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
>
--
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
