Hello,
I’m getting the following error trying to authenticate.
I’m using AD for password storage. I this did work in RC1 I’m at a loss as to
what might be broken. Any help would be greatly apricated.
2019-02-08 16:30:35,551 DEBUG
Thanks Ray for staying on this!!
I finally figured this out. My Login page is loading some JS and CSS file.
One of the JS does not exist, returning 404. That apparently caused the
problem. Once I removed that non-existing JS, it works!
Yan
On Thursday, February 7, 2019 at 7:31:02 PM UTC-5,
The logs following for OIDC flow:
2019-02-08 11:46:26,662 DEBUG
[org.apereo.cas.web.flow.actions.RedirectToServiceAction] - https://idp-oidc.fr/oauth2.0/callbackAuthorize?client_id=service.clientId_uri=service.redirect_uri_type=code_name=CasOAuthClient,
All logs normal OIDC flow
2019-02-08 11:44:30,863 DEBUG
[org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver] -
2019-02-08 11:44:30,863 DEBUG
[org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver] -
2019-02-08 11:44:30,863 DEBUG
Here my logs for normal OIDC flow:
2019-02-08 11:44:30,863 DEBUG
[org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver] -
2019-02-08 11:44:30,863 DEBUG
[org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver] -
2019-02-08 11:44:30,863 DEBUG
Hi Andy,
Here are my cas.log about OIDC + delegation SAML2:
2019-02-08 09:36:20,832 DEBUG
[org.apereo.cas.oidc.web.OidcCasClientRedirectActionBuilder] -
2019-02-08 09:36:21,167 INFO
[org.apereo.cas.web.flow.login.InitialFlowSetupAction] -
2019-02-08 09:36:21,167 INFO
