In docs

In order to allow CAS to support and respond to attribute queries, you need 
to make sure the generated metadata has the AttributeAuthorityDescriptor 
element 
enabled

I noticed that when i put

cas.authn.samlIdp.attributeQueryProfileEnabled=true


in idp-metadata.xml tag AttributeAuthorityDescriptor commented and it is 
ignoring my flag

четверг, 6 июня 2019 г., 4:19:39 UTC+3 пользователь Andy Ng написал:
>
> Hi Andrey,
>
> I do know for a fact that my CAS 5.3.x is running with SAML as idp and 
> connecting to other SAML sp just fine (multiple SAML client, including 
> SimpleSAMLPHP), no need modify the generated idp-metadata.xmp for me.
>
> So... Maybe if you still can't successfully connect to SAML, it could be 
> the following:
> - Maybe CAS 6 have bug
> - Maybe keycloak doesn't actually return the attribute to you (highly 
> doubt it)
> - Maybe your config is wrong (which is unlikely, from what you provide it 
> seems the config is ok)
>
> So, maybe try using CAS 5.3.x and see if that work? CAS 5 to 6 have a big 
> jump, so it is possible that there is some obscure bug that discovered 
> first by you.
>
> - Andy
>

-- 
- 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/edc84853-7aed-4220-a78a-bec1a743fc45%40apereo.org.

Reply via email to