I'm using CAS-Flask <https://github.com/cameronbwhite/Flask-CAS> because it's quick and easy to test with. I have it printing out all attributes it recieves from CAS, it is receiving none. So I expect to recieve a list of my name, last name, and email, but get nothing. But perhaps I'm testing wrong? Do you have a suggestion on how to go about testing what I'm getting from CAS?
There is no reason to separate those first two steps. Originally I had them combined, but it wasn't working, so I separated them in an effort to try everything. No dice. The any and all applications is correct for now. I figured I could figure out how to restrict it once I established that I'm actually getting attributes to flow through. This is dev so it doesn't matter. On Friday, February 23, 2018 at 3:37:33 PM UTC-6, Misagh Moayyed wrote: > > What do you expect to happen, and what is actually happen that you > consider erroneous? How are you testing the attribute release bit? > > Not having verified every setting, your config below says: authenticate > with ldap, fetch attributes from ldap and release 3 attributes to any and > all applications. The first two steps can be combined unless you have good > reason not to. > > --Misagh > > ------------------------------ > > *From: *"Toby Archer" <sand...@gmail.com <javascript:>> > *To: *"CAS Community" <cas-...@apereo.org <javascript:>> > *Sent: *Friday, February 23, 2018 1:36:32 PM > *Subject: *[cas-user] Stumped on attribute release in CAS 5.1 > > I'm trying to figure out how to do attribute release and haven't gotten > anywhere. I've read all the pages like this one: > https://apereo.github.io/cas/5.1.x/integration/Attribute-Release-Policies.html > > and tried searching this mailing list and followed instructions like in > this one: > https://groups.google.com/a/apereo.org/forum/#!searchin/cas-user/attribute/cas-user/VVaONIp1Ts0/Hedpv2uGAwAJ > > Right now I'm using ldap for both authentication and attributes. The > relevant part of my cas.properties file looks like this: > > # LDAP Auth > cas.authn.ldap[0].type=AUTHENTICATED > cas.authn.ldap[0].ldapUrl=ldap://usd-ldap.usd.edu > cas.authn.ldap[0].baseDn=o=usd.edu > cas.authn.ldap[0].userFilter=uid=%u > cas.authn.ldap[0].subtreeSearch=true > cas.authn.ldap[0].bindDn=cn=Directory Manager > cas.authn.ldap[0].bindCredential=password > cas.authn.ldap[0].userFilter=uid={user} > cas.authn.ldap[0].dnFormat=uid=%s,ou=people > cas.authn.ldap[0].keystore=file:/etc/cas/thekeystore > cas.authn.ldap[0].keyStorePassword=password > cas.authn.ldap[0].name=dev-ldap7-1 > > cas.authn.ldap[0].allowMissingPrincipalAttributeValue=true > cas.authn.ldap[0].principalAttributeList=cn,sn,mail > > cas.authn.attributeRepository.defaultAttributesToRelease=cn,sn,mail > > cas.authn.attributeRepository.stub.attributes.uid=uid > cas.authn.attributeRepository.stub.attributes.displayName=displayName > cas.authn.attributeRepository.stub.attributes.cn=commonName > > cas.authn.attributeRepository.ldap[0].type=AUTHENTICATED > cas.authn.attributeRepository.ldap[0].ldapUrl=ldap://usd-ldap.usd.edu > cas.authn.attributeRepository.ldap[0].baseDn=o=usd.edu > cas.authn.attributeRepository.ldap[0].userFilter=uid=%u > cas.authn.attributeRepository.ldap[0].subtreeSearch=true > cas.authn.attributeRepository.ldap[0].bindDn=cn=Directory Manager > cas.authn.attributeRepository.ldap[0].bindCredential=password > cas.authn.attributeRepository.ldap[0].userFilter=uid={user} > cas.authn.attributeRepository.ldap[0].dnFormat=uid=%s,uo=people > cas.authn.attributeRepository.ldap[0].keystore=file:/etc/cas/thekeystore > cas.authn.attributeRepository.ldap[0].keyStorePassword=password > cas.authn.attributeRepository.ldap[0].name=dev-ldap7-1 > > cas.authn.attributeRepository.ldap[0].uid=uid > cas.authn.attributeRepository.ldap[0].displayName=displayName > cas.authn.attributeRepository.ldap[0].cn=commonName > cas.authn.attributeRepository.ldap[0].mail=mail > cas.authn.attributeRepository.ldap[0].sn=sn > > There are configurations for a couple of different attempts, but > regardless of what I do get back no attributes. The docs talk about the > personDirectory but either don't give instructions on how to configure it > or give instructions for cas 4. I'm at a bit of a loss on what to do. Any > advise out there? > > -- > - Website: https://apereo.github.io/cas > - Gitter Chatroom: https://gitter.im/apereo/cas > - List Guidelines: https://goo.gl/1VRrw7 > - Contributions: https://goo.gl/mh7qDG > --- > You received this message because you are subscribed to the Google Groups > "CAS Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to cas-user+u...@apereo.org <javascript:>. > To view this discussion on the web visit > https://groups.google.com/a/apereo.org/d/msgid/cas-user/c0327b4c-528a-476f-8e2e-e5ee82024744%40apereo.org > > <https://groups.google.com/a/apereo.org/d/msgid/cas-user/c0327b4c-528a-476f-8e2e-e5ee82024744%40apereo.org?utm_medium=email&utm_source=footer> > . > > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/57b62e57-ab38-4111-b60f-6715ae5c7b4b%40apereo.org.
