Really stupid question about IdP v3 CAS support

[Walter Forbes Hoehn (wassa)]

Depending on what client is being used (and thus what configuration options are presented), they will usually either ask for URLs for the login and validation endpoints or they will request a base URL (some clients refer to this as a “prefix”) from which the two are inferred.

The base URL is: https://$HOST/idp/profile/cas/

Thus, the login URL is: https://$HOST/idp/profile/cas/login

The validation URL varies depending on what style of validation you are doing.

-WFH


> On Jul 1, 2016, at 1:13 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
>> Depending on your setup, you will likely need to add an entry to cas-
>> protocol.xml. If the application doesn’t need any attributes besides the
>> username, you are done.  To send attributes, you’ll also need to edit the
>> standard filter configuration.
> 
> I think she's asking more about what they will ask from her, and the answer is that there is no metadata in CAS and its security model is much different. All they will ask is the location of your CAS server. I think even the paths/locations of the CAS ticket validation and request endpoints are hardwired in the protocol (SAML's are not, we never even considered that would fly, shows what making crazy assumptions can buy you).
> 
> -- Scott
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net