<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div>
<div id="appendonsend" style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
A long time ago, we had /cas as our endpoint when we used Apereo CAS. When we migrated to Shibboleth, we used these Apache rewrite rules:</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
# Rewrite cas URLs to Shibboleth
<div> RewriteRule ^/cas/+serviceValidate$ /idp/profile/cas/serviceValidate [PT]</div>
<div> RewriteRule ^/cas/+proxyValidate$ /idp/profile/cas/proxyValidate [PT]</div>
<div> RewriteRule ^/cas/+samlValidate$ /idp/profile/cas/samlValidate [PT]</div>
<div> RewriteRule ^/cas/+validate$ /idp/profile/cas/validate [PT]</div>
<div> RewriteRule ^/cas/+(.+)$ /idp/profile/cas/$1 [R,NE,L]</div>
<div><br>
</div>
We still have these in place today, working fine.</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Andy<br>
</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> users <users-bounces@shibboleth.net> on behalf of Cantor, Scott <cantor.2@osu.edu><br>
<b>Sent:</b> Thursday, January 21, 2021 9:31 AM<br>
<b>To:</b> Shib Users <users@shibboleth.net><br>
<b>Subject:</b> Re: Shibboleth IdP 4.0.1 and CAS</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">[This email originated from outside of OSU. Use caution with links and attachments.]<br>
<br>
On 1/21/21, 11:54 AM, "users on behalf of Max via users" <users-bounces@shibboleth.net on behalf of users@shibboleth.net> wrote:<br>
<br>
> It seems that the /cas and /sCAS Context Roots are no longer present.<br>
<br>
Neither have ever existed. CAS flows live under /idp/profile/cas and are automatically registered and logged at startup. Trying to run them at other locations is something that theoretically can be done but has never been tested to my knowledge.<br>
<br>
> In the file %{idp.home}/conf/services.xml the CASServiceRegistryResources is<br>
> enabled:<br>
<br>
That has nothing to do with the processing of requests in the path handling sense, a 404 is a fundamentally broken container or webapp not starting up to begin with.<br>
<br>
> These are the entries we have in the idp-process.log file related to CAS<br>
> during startup:<br>
<br>
It logs all the flow definitions and their locations at startup before that ever happens, but the literal notion of anything but /idp as a context root (or I guess anything else, doesn't literally have to be /idp), that doesn't exist. There's one context root
and it usually lives at /idp<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg">
https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br>
</div>
</span></font></div>
</div>
</body>
</html>