Sry its ok,
i have used
<bean id="attributeRepository"
class="org.jasig.cas.persondir.LdapPersonAttributeDao"
p:baseDN="ou=people,dc=mycompany,dc=fr"
p:searchFilter="uid={0}"
p:searchControls-ref="searchControls"
p:connectionFactory-ref="searchPooledLdapConnectionFactory"
p:resultAttributeMapping-ref="resultAttributeMap"
/>
<!-- Originally had a queryAttributeMapping-ref in here as well -->
<!-- removing the queryAttribute.... got things working -->
<util:map id="resultAttributeMap">
<entry key="uid" value="user" />
<entry key="mail" value="email" />
<entry key="cn" value="displayName" />
<entry key="eduPersonPrincipalName" value="eduPersonPrincipalName" />
</util:map>
<bean id="searchControls"
class="javax.naming.directory.SearchControls"
p:searchScope="2"
/>
instead my old bean attributeRepository and now its ok
bye
-----------------------------------------------------------------
Daniel CHARLOT
D.S.I. Université de Nice Sophia-Antipolis
Administrateur Systèmes et Réseaux
28, avenue de Valrose - BP 2135 - 06103 NICE
Tél : 04-92-07-67-07
Le 1 sept. 2014 à 16:09, [email protected] a écrit :
> Hi, I think my problem is similar.
>
> I have in my deployerConfigContext.xml
>
> " <util:map id="attrRepoBackingMap">
> <entry key="uid" value="uid" />
> <entry key="eduPersonAffiliation" value="eduPersonAffiliation" />
> <entry key="groupMembership" value="groupMembership" />
> </util:map> »
>
> but when i have use in my php application : phpCAS::getAttributes();
> my result is uid, eduPersonAffiliation, groupMembership but not the content
> of my variable.
>
> Anyone knows how to resolved this problem?
>
> I have tried to copy
>
> /tomcat/webapps/cas/WEB-INF/view/jsp/protocol/3.0/casServiceValidationSuccess.jsp
> to /tomcat/webapps/cas/WEB-INF/view/jsp/protocol/2.0/
> but nothing changes.
>
> Thanks a lot.
>
> -----------------------------------------------------------------
> Daniel CHARLOT
> D.S.I. Université de Nice Sophia-Antipolis
> Administrateur Systèmes et Réseaux
> 28, avenue de Valrose - BP 2135 - 06103 NICE
> Tél : 04-92-07-67-07
>
>
>
>
>
>
>
>
>
>
>
> Le 6 août 2014 à 12:52, Misagh Moayyed <[email protected]> a écrit :
>
>> It is the recommended approach. Come to think of, we probably should include
>> that either in the protocol or somewhere on the docs page.
>>
>> From: [email protected] [mailto:[email protected]]
>> Sent: Wednesday, August 6, 2014 3:30 AM
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> I can indeed – and it works! :-D
>>
>> Is /p3/serviceValidate the recommended approach when you want to use v3.0 of
>> the protocol then? Or is it a workaround?
>>
>> Thanks again for all the help and for such quick respnses.
>>
>> Regards,
>>
>> Richard
>>
>> From: Misagh Moayyed [mailto:[email protected]]
>> Sent: 06 August 2014 11:24
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> Can you point your client to /p3/serviceValidate instead?
>>
>> From: [email protected] [mailto:[email protected]]
>> Sent: Wednesday, August 6, 2014 3:21 AM
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> Yep, that was it. I’ve (hopefully temporarily) copied the 3.0 version of
>> casServiceValidationSuccess.jsp to 2.0 and it now shows the attributes.
>>
>> So all I now need is to be able to tall CAS I want it to use the 3.0 version
>> of casServiceValidationSuccess.jsp.
>>
>> Regards,
>>
>> Richard
>>
>> From: [email protected] [mailto:[email protected]]
>> Sent: 06 August 2014 11:14
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> I think I’ve found the problem!
>>
>> It’s using casServiceValidationSuccess.jsp from
>> "WEB-INF/view/jsp/protocol/2.0" not "WEB-INF/view/jsp/protocol/3.0". Surely
>> it should default to the 3.0 one if there are attributes, shouldn’t it? I
>> can’t find any way of telling CAS that I am using the v3 protocol when I
>> make the serviceValidate call…
>>
>> Regards,
>>
>> Richard
>>
>> From: [email protected] [mailto:[email protected]]
>> Sent: 06 August 2014 10:28
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> Thanks – that definitely helped!
>>
>> I’m getting there now. My log now contains:
>>
>> 2014-08-06 10:20:45,521 DEBUG
>> [org.jasig.cas.services.support.RegisteredServiceDefaultAttributeFilter] -
>> Found attribute [billingAccountId] in the list of allowed attributes for
>> service [HTTP Services]
>> 2014-08-06 10:20:45,521 DEBUG
>> [org.jasig.cas.services.support.RegisteredServiceDefaultAttributeFilter] -
>> Found attribute [groupMembership] in the list of allowed attributes for
>> service [HTTP Services]
>> 2014-08-06 10:20:45,522 DEBUG
>> [org.jasig.cas.services.support.RegisteredServiceDefaultAttributeFilter] -
>> Found attribute [uid] in the list of allowed attributes for service [HTTP
>> Services]
>>
>> Still no attributes in the XML from serviceValidate though…
>>
>> Regards,
>>
>> Richard
>>
>> From: Misagh Moayyed [mailto:[email protected]]
>> Sent: 06 August 2014 10:07
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> Answers inline.
>>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]]
>> Sent: Wednesday, August 6, 2014 1:41 AM
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> Thanks.
>>
>> So does "CAS is not looking at your handler for attributes" mean that the
>> attributes supplied via the SimplePrincipal object are not being used?
>>
>> Correct.
>>
>>
>> When you refer to "3 hardcoded attributes" do you mean this block...?
>>
>> <util:map id="attrRepoBackingMap">
>> <entry key="uid" value="uid" />
>> <entry key="eduPersonAffiliation" value="eduPersonAffiliation" />
>> <entry key="groupMembership" value="groupMembership" />
>> </util:map>
>>
>> Yes.
>>
>> And if so, presumably because only uid and groupMembership are listed as
>> allowedAttributes, only these two can be released? (Currently, no
>> attributes are coming through into the serviceValidate response XML.)
>>
>> Yes.
>>
>> Also, when you say "null out the resolver" do you mean
>> primaryPrincipalResolver? When I do that, my primaryAuthenticationHandler
>> no longer works (or is used). Apologies, but I don't yet understand enough
>> about CAS to confidently make assumptions!
>>
>> See:
>> http://jasig.github.io/cas/development/installation/Configuring-Authentication-Components.html#principalresolver-vs-authenticationhandler
>>
>>
>> I'll turn on debug and see what it says.
>>
>> Regards,
>>
>> Richard
>>
>>
>>
>> -----Original Message-----
>> From: Misagh Moayyed [mailto:[email protected]]
>> Sent: 06 August 2014 09:24
>> To: [email protected]
>> Subject: RE: [cas-user] Java-sourced custom attributes not being released
>>
>> CAS is not looking at your handler for attributes; it will take a look at
>> your resolver which right now has 3 hardcoded attributes, two of which can
>> be released. (if you want the handler to take precedence, null out the
>> resolver) If you are not getting those two, up the CAS logging to DEBUG and
>> see what's coming out.
>>
>> -----Original Message-----
>> From: Richard Wiseman [mailto:[email protected]]
>> Sent: Wednesday, August 6, 2014 12:58 AM
>> To: [email protected]
>> Subject: RE:[cas-user] Java-sourced custom attributes not being released
>>
>> There are lots of commented-out elements from my various attempts and I've
>> scrubbed out the database details but here it is.
>>
>> Thanks!
>> --
>> 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,
>> seehttp://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,
>> seehttp://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
>>
>> --
>> 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
>>
>> --
>> 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
>>
>> --
>> 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
>
> --
> 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
