The issue could be with what the request is asking for (such as scope, etc.)
and the service not being configured to release them.
My test client (created with cas management application):
{"@class":"org.apereo.cas.services.OidcRegisteredService",
I've found the issue, it was coming from the service file not loaded by
cas. I've added the following line to my cas.properties :
*cas.service-registry.json.location=file:/C:/Program Files/Tomcat
9.0/etc/cas/config*
But now I'm having a new error :
2023-07-11 14:20:47,712 ERROR
Indeed redirect_uri wasn't consistent between conf, but after updating it
nothing has changed.
This is my service file now :
{
"@class": "org.apereo.cas.services.OidcRegisteredService",
"serviceId": "http://localhost:3000;,
"name": "OIDC",
"id": 1,
"clientId":
Jérémie,
The redirect_uri in the URL sent to cas must match the serviceId in your
service file. serviceId can be a regex. The client_id matches clientId (this is
more obvious).
There may be other parameters that are sent to cas by your application that are
not identified in the service file.
Hi,
I'm simply getting :
*2023-07-10 06:31:50,609 INFO [org.apereo.cas.web.CasWebApplicationReady] -
2023-07-10
06:32:21,021 INFO
[org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <[0]
expired tickets removed.>2023-07-10 06:33:48,750 WARN
Jérémie,
What do the cas logs say about the authentication event (may need debug level)?
The authorize URL comes after the authentication step. Are you logged in, in
that browser?
Ray
On Tue, 2023-06-27 at 06:30 -0700, Jérémie wrote:
Notice: This message was sent from outside the University
Hi,
I'm pretty new to cas (6.6.8) and I'm trying to connect an test application
to my CAS server using OIDC. I'm used to Okta, Auth0, etc so OIDC is not
new to me, just CAS configuration.
My Cas is also connected to an AD to sign in.
This is my Cas server configuration using OIDC module
