Re: [cas-user] Java-sourced custom attributes not being released
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 mmoay...@unicon.net 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: richard.wise...@bt.com [mailto:richard.wise...@bt.com] Sent: Wednesday, August 6, 2014 3:30 AM To: cas-user@lists.jasig.org 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:mmoay...@unicon.net] Sent: 06 August 2014 11:24 To: cas-user@lists.jasig.org Subject: RE: [cas-user] Java-sourced custom attributes not being released Can you point your client to /p3/serviceValidate instead? From: richard.wise...@bt.com [mailto:richard.wise...@bt.com] Sent: Wednesday, August 6, 2014 3:21 AM To: cas-user@lists.jasig.org 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: richard.wise...@bt.com [mailto:richard.wise...@bt.com] Sent: 06 August 2014 11:14 To: cas-user@lists.jasig.org 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: richard.wise...@bt.com [mailto:richard.wise...@bt.com] Sent: 06 August 2014 10:28 To: cas-user@lists.jasig.org 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:mmoay...@unicon.net] Sent: 06 August 2014 10:07 To: cas-user@lists.jasig.org Subject: RE: [cas-user] Java-sourced custom attributes not being released Answers inline. -Original Message- From: richard.wise...@bt.com [mailto:richard.wise...@bt.com] Sent: Wednesday, August 6, 2014 1:41 AM To: cas-user@lists.jasig.org 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
Re: [cas-user] Java-sourced custom attributes not being released
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, daniel.char...@unice.fr 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 mmoay...@unicon.net 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: richard.wise...@bt.com [mailto:richard.wise...@bt.com]
Sent: Wednesday, August 6, 2014 3:30 AM
To: cas-user@lists.jasig.org
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:mmoay...@unicon.net]
Sent: 06 August 2014 11:24
To: cas-user@lists.jasig.org
Subject: RE: [cas-user] Java-sourced custom attributes not being released
Can you point your client to /p3/serviceValidate instead?
From: richard.wise...@bt.com [mailto:richard.wise...@bt.com]
Sent: Wednesday, August 6, 2014 3:21 AM
To: cas-user@lists.jasig.org
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: richard.wise...@bt.com [mailto:richard.wise...@bt.com]
Sent: 06 August 2014 11:14
To: cas-user@lists.jasig.org
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: richard.wise...@bt.com [mailto:richard.wise...@bt.com]
Sent: 06 August 2014 10:28
To: cas-user@lists.jasig.org
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
Re: [cas-user] Java CAS Client 3.2.2 ?
If I make the following changes I can get a 3.2.2 build: 1. Ignore Saml11TicketValidatorTests (its running into some issue with the way it starts the server; apparently we ignore these on master which is weird) 2. Update Spy Memcache Client to latest version (only more recent versions are in Maven Central) 3. Update Atlassian repository to new location I am assuming no one has any issue with these changes to get a 3.2.2 build out. If not, I'll cut the release tomorrow night. On Fri, Aug 29, 2014 at 9:28 AM, Marvin Addison marvin.addi...@gmail.com wrote: https://github.com/Jasig/java-cas-client/pull/81 Wrong base branch. Let's try again: https://github.com/Jasig/java-cas-client/pull/82 M -- You are currently subscribed to cas-user@lists.jasig.org as: scott.battag...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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
