or PHP) possibly create an egregious number of
> handles? This would likely show in error messages printed to the logs.
> lsof could also be your friend here.
>
> Matt
>
>
> On May 19, 2017 11:15 AM, "Neil Sabol" <neil@gmail.com >
> wrote:
>
> Hello
Hello CAS Community,
I hope this message finds you all well.
As time permits, I am hoping to pick your brains about a mysterious issue
we experienced recently with mod_auth_cas (suspect it was not mod_auth_cas
itself but something related).
We have been running mod_auth_cas (version 1.1) in
Hello Pouria, All,
To build on David's response, you should be able to echo out the HTTP Headers
on the server side with whatever language you are using.
For example, in PHP see http://php.net/manual/en/function.getallheaders.php
(Example #1) - just create a test page in your DocumentRoot,
Hi David,
We’ve had mixed results with mod_auth_cas logout.
One way we have overcome this is using a separate, intermediary (non-CAS)
logout page to:
· Remove the MOD_AUTH_CAS and MOD_AUTH_CAS_S cookies from the user’s
session
· Redirect the user to the CAS logout page.
We
, Neil Sabol a écrit :
Hi Jay,
Good question – we struggled with this a little while ago and devised a
solution that worked for our Angular JS applications. This may or may not scale
or apply to your situation.
We discovered that mod_auth_cas “sees” routes in Angular (based on URI anyway).
We
Hi Jay,
Good question – we struggled with this a little while ago and devised a
solution that worked for our Angular JS applications. This may or may not scale
or apply to your situation.
We discovered that mod_auth_cas “sees” routes in Angular (based on URI anyway).
We configured
Hello Valentine,
Although I’m not familiar with the exact process in .NET, I believe this is
something you handle in your application.
Basically, you need to redirect to the CAS logout URL with the service
parameter set to the URL you want to redirect to once CAS logout occurs.
Example:
