On Friday, 25 May 2018 01:57:49 UTC+8, Lionel Samuel wrote:
> Echoing Andy :)
> Andy -- thank you also for your all your posts -- we have googled on
> issues we faced -- your, David, and a few others have posted responses that
> were extremely helpful! Apereo should have a lists of
Is there a way to use ajp with the cas-management-overlay?
I am using ajp with cas-overlay 5.2.4, but it uses the tomcat appserver -
and it doesn't look like that is available yet for the
The settings for my cas-overlay are as follows:
Seems so obvious now that you say it. Thank you very much, works like a
On Thu, May 24, 2018 at 12:14 PM, David Curry
> The "root" of the web server, i.e., where "https://casserver/cas; points,
> is the ".../webapps/cas/WEB-INF/classes/static" directory.
Absolutely that would work. I think I am still doing something wrong
though. I have timedOut.html under templates next to casLoginView.html etc.
When I redirect to /cas/timedOut.html it gives me a cas page not found
page. When I redirect to /timedOut.html it says my page is not found on the
How strongly do you feel about having "https://server/cas/timeout; as
opposed to "https://server/cas/timeout.html;?
If you're fine with the latter, you should just be able to drop
"timeout.html" into the same place where all the other casWhateverView.html
pages are and redirect to
I am trying to provide a timeout page to redirect to when a timer on my
login page goes off. I can get it to redirect, but there is no page so it
just goes to the not found page. Is there an easy way to route an extra
page so I can go to https://server:8443/cas/timeOut?
Or how would I go about
I have this requirement where we're supposed to allow users to sign-in with
either an email address or a phone number.
1) Can I tailor CAS for either of those 2 options?
2) When it comes to attributes, how do I pair that user (because the user
id is different) with the attributes clause?
That got it! Thank you so much, David!
- 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
Echoing Andy :)
Andy -- thank you also for your all your posts -- we have googled on
issues we faced -- your, David, and a few others have posted responses that
were extremely helpful! Apereo should have a lists of names to recognize
those that have been very supportive of the CAS community.
Thanks David :)
This was exactly what we needed.
On Wednesday, May 23, 2018 at 5:01:29 AM UTC-7, David Curry wrote:
> These two threads are somewhat helpful:
On the Attribute Release tab for a service in service manager.
You may also have to set a list of released attributes in management.properties:
# --- Global Attributes --- #
In my old CAS installation, I have attribute mapping that looks like this
I'm not sure what you mean by the logoutUrl "supporting" SLO. If you mean
will SLO suddenly start working just because you put a value in that
property, then the answer is no.
The logoutUrl property is exactly what the documentation says it is -- a
way to let an application receive a logout
Firstly thanks for your response and clarifying few things. My query to you
Does logoutUrl property support SLO? If so, which all cookie should I be
On Thu, May 24, 2018 at 6:17 PM, David Curry
> What do you mean when you say you
You do not need the CAS Management Overlay to enable the above; it's
accomplished with just some settings in cas.properties and creating the
user file and a service registry entry.
If you'd like step-by-step
What do you mean when you say you are "using mod_auth_cas for reverse proxy
to my cas server"? Mod_auth_cas is not a (reverse) proxy. It's simply a way
to control access to content on an Apache web server using CAS
authentication. Think of it as an alternative to HTTP Basic Authentication.
I am using CAS 5.2.4. I would like to know if its possible to create a
custom ticket registry cleaner. I would like to log the user out of system
database at the time of ticket clean up.
I looked at cas-server-core-api-ticket and cas-server-core-tickets jars. I
could not find a config
there is a massive performance issue with ProxyGrantingTickets with JPA
TicketRegistry if there are a lot of ProxyGrantingTickets created for one
I am using CAS 5.2.4. I have a custom logout handler registered and working
properly. It logs the user out from our database. This works perfectly fine
when I hit /logout endpoint.
But when the TGC expires the user logs out of the CAS but is still logged
in to the database. I would expect
Attaching the version page.
On Thursday, May 24, 2018 at 3:14:05 AM UTC-5, Jay wrote:
> Hello everyone,
> In our old CAS3.x version, we had the health page and version monitor
> I am trying to figure if we have something similar in CAS5.3.x framework.
> Health Page and Version page
In our old CAS3.x version, we had the health page and version monitor page.
I am trying to figure if we have something similar in CAS5.3.x framework.
Health Page and Version page looks something like this.
We have enabled the User acceptance policy.
Whenever I use incognito window in Chrome and login it does not shows the
User Policy page to accept. Only the first time I could see but closing and
opening a new windows does not show the policy page.
Any help here is much appreciated.
I am using Mod_auth_cas for reverse proxy to my cas server. How do I achive
slo and sso using mod_auth_cas? Also when I logout I am still able to
access my application without authentication. Is this the way mod_auth_cas
Mail list logo