This seems to have been fixed in 6.2.0 RC2, I have not had the error at all
on 6.2.0 RC2, I then spend a bit of time finding a reliable sequence of
events that caused the error and found a way to reproduce consistently on
6.1.2 following a specific series of login/logout requests:
In the same
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="
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
Indeed it was something extremely basic, I had forgotten to set the CAS
server name and prefix. Remember to set:
cas.server.name=https://cas.mydomain.com
cas.server.prefix=https://cas.mydomain.com/cas
Thank you again for a great product!
On Wednesday, May 1, 2019 at 5:16:21 PM UTC+5:30,
