Ok I just wanted to make sure. Thanks!
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Man H
Sent: Friday, December 15, 2017 9:39 AM
Subject: Re: [cas-user] 5.1.2 to 5.2 CAS migration
this is what I have in 5.2.0
CREATE TABLE `RegexRegisteredService`
I am getting the same error along with . I will let you know if I find
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Duane Booher
Sent: Tuesday, November 21, 2017 11:44 AM
To: CAS Community
Subject: [cas-user] ehcache
this is what I have in 5.2.0
CREATE TABLE `RegexRegisteredService` (
`expression_type` varchar(50) NOT NULL DEFAULT 'regex',
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`description` varchar(255) DEFAULT NULL,
I try since a too long time to make JWT Service Ticket works.
no problerm with dependencies cas-server-support-token-tickets (and
cas-server-support-token-webflow) in pom.xml
In cas.properties (version 5.2.0, names of parameters have changed)
## JWT authentification :
Thank you, that solved it.
Von: firstname.lastname@example.org [mailto:email@example.com] Im Auftrag von David Curry
Gesendet: Freitag, 15. Dezember 2017 14:13
Betreff: Re: [cas-user] Exception in async processing
This is a servlet container configuration issue, not a code issue
That really helped. I finally have ldap working. You filled in some gaps
for me. But I did have one remaining problem that I had to resolve. Our
AD certs are self signed for ldap. The chain cert wasn’t trusted by just
loading the public cert. So I had to get the CA and install it
I think you should leave cas.server.httpProxy.secure=true, this is actually
setting on container connector the CAS is checking.
On Thursday, December 14, 2017 at 5:50:59 AM UTC+1, casuser wrote:
> There is a load balancer in between the user and the CAS . The load
> balancer will check
This is a servlet container configuration issue, not a code issue -- no pr
needed. The embedded servlet container comes pre-configured with async
support enabled, but if you're using an external servlet container, you
have to enable it yourself. This is documented here:
I'm trying configure CAS as OAUTH2 Server, to manage SPA security using
password grant_type. The problem is that the CAS Server ignores the
username and password parameters. Password grant type behaviuor is the same
that client_credentials grant type.
I had exactly the same issue.
Anyone has found a workaround ?
- 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
I'm running CAS 5.2.0 on seperate tomcat. Trying to access the
status/ssosessions page, I get the following exception:
java.lang.IllegalStateException: Async support must be enabled on a servlet and
for all filters involved in async request processing. This is done in Java code
Mail list logo