Hi All, the other day we noticed that the "issuer" field in access tokens provided by our CAS via a OIDC service does not contain the issuer configured in our application.yaml under "cas.authn.oidc.issuer". The id token on the other hand does contain the correct issuer.
After digging into the code we found that the issuer in the access token does obviously not us this property, instead we see that the "cas.server.prefix" is used. Our conclusion was that the access token generated is part of the oauth2.0 standard and therefore does not use the OIDC issuer configuration we provided which makes sense in a way. The id token is using the provided OIDC issuer because it is part of the OIDC standard. One thing that still bothers us is that we are not able to configure the issuer in the tokens to contain the same value. For OIDC we configure "cas.authn.oidc.issuer=<domain>/oidc" and our "cas.server.prefix=<domain>". The "/oidc" is needed because some of our clients need this path to be able to then automatically resolve to the "/oidc/.well-known" with their framework. Did anyone had similar issues and has a good idea how to be able to solve this in a proper way? Thanks in advance -- - 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 Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/77ef884a-d756-4716-a474-6964ccd8f1c7n%40apereo.org.
