Hi all,
I'm testing CAS 6.1.2 in an external Jetty (9.4.24) container, and I've been
running into an issue where CAS logs an error message like the following:
User limit of inotify instances reached or too many open files
Prior to a huge stack trace and the application shutting down.
I origina
I resolved this myself by looking closer at what you posted, when
specifying "redirect_uri" in Azure AD for OpenID Connect (OIDC).
The redirect_uri should be:
https://cas.mydomain.com/cas/login/clientName
where clientName is the property specified at "cas.authn.pac4j.oidc[0].
azure.clientName="
Hello
Using cas 6.1.2 and compiled cas-management (master branch, thanks to
Travis et.al) for fixing the attribute and pac4J compatible changes and 6.x
tree.
Trying
this: https://apereo.github.io/2019/05/13/cas61x-mfa-selection-strategies/
Assigned: cas.authn.mfa.provider-selection-e
Hello. Do you happen to know if this patch is applicable to 6.1.x tree as
well or only 6.2.x?
Thanks.
--
- 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
Update: patched! Thanks for the tip, Nono!
--
- 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
Hi bottlecheck,
After you set your cas.server.name and cas.server.prefix, what did you end
up setting as the "redirect_uri" in Azure AD configuration?
Thanks in advance for your help
On Wednesday, May 1, 2019 at 8:13:43 AM UTC-6, bottlecheck wrote:
>
> Indeed it was something extremely basic, I h
Jeremy,
I should have walked through the full life cycle when I checked. I do have
JSESSIONID cookie on logout and it does not have an expiration date.
It seems odd that it affects delegated auth. I do not have anything set up to
test it.
Ray
On Fri, 2019-12-20 at 08:44 -0800, Jeremy Whaley wr
Ray,
The JSESSIONID cookie is created when I logout of CAS. It is a session
cookie with the path /cas. If I delete that cookie manually from my
browser's storage, I can log back in successfully. I can also achieve the
same result by closing the entire browser (which removes the session
cookie)
What do you mean by service definition as CAS prefix?
On Fri, 20 Dec 2019, 2:46 pm Cemal Önder,
wrote:
> Core dev Misagh Moayyed mentioned that this is a bug:
> https://stackoverflow.com/questions/59368162/cas-rest-protocol-does-not-work-without-generic-service-definition/
>
> So a solution is t
Ray,
I finally solved my problem by adding secure="true" in my Tomcat Connector
which is used by Apache with proxyHttp.
Have a good week-end and thanks for your help.
Mickaël
Le jeudi 19 décembre 2019 18:55:24 UTC+1, rbon a écrit :
>
> Mickaël,
>
> Could this be related to self signed certifi
I am using CAS 5.1.1 which comes with pac4j 2.0.0
On Friday, December 20, 2019 at 8:34:55 AM UTC+1, leleuj wrote:
>
> Hi,
>
> Which version of CAS (and pac4j) do you use? Do you have one or more CAS
> servers?
> Thanks.
> Best regards,
> Jérôme
>
> Le jeu. 19 déc. 2019 à 17:28, Filip Majernik >
11 matches
Mail list logo
