On Thu, 24 Oct 2019 at 08:44, David Curry <[email protected]> wrote:
>
> You should be safe from SAML messes; CASv2 attribute release via SAML 1.1 has 
> been around for years and years; much longer than the CAS server's support 
> for the SAML2 protocol and acting as an IdP/SP. You don't actually have to 
> configure anything at all; just use the other endpoint (samlValidate instead 
> of serviceValidate).

Note that you can use /serviceValidate with mod_auth_cas v1.2 if your
server releases attributes.

> CASAuthnHeader is an on/off attribute. (See the documentation: 
> https://github.com/apereo/mod_auth_cas). If you want to change the attribute 
> headers to start with something other than "CAS_", that's the 
> CASAttributePrefix directive.

CASAuthNHeader specifies the name of a header. It is used like:

CASAuthNHeader username

-- 
- 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/CAAgu-wC_eCURZNpGzC%2BLQGaLzN7yWk9b7L0KjS7eYk9u%2Bb6tGA%40mail.gmail.com.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to