Greetings, I am working with CAS 5.2.2 and trying to authenticate an existing client application [Client app is using a UAA server (https://github.com/cloudfoundry/uaa)] that supports OIDC.
The call to: /cas/oidc/authorize is succeeding. The problems happen when the client (server side [not browser]) tries to call: cas/oidc/accessToken/ the following parameters are passed with this call: grant_type=authorization_code code=OC-13-INRciVjflpa1elco2HOuIvOSNlTRIRT4fPO response_type=id_token redirect_uri=https://localhost:1238/login/callback/cas I can debug the CAS 5.2.2 server and see that the call is failing with a "Could not locate authenticated profile for this request". The root cause for this failure is that no profile is being returned from the ProfileManager.retrieveAll method. There is neither a profile stored in the request or stored in the session. It makes sense that there is no profile stored in the session because it is a (client) UAA server side HTTP Request that is calling '/cas/oidc/accessToken', i.e. not the browser. Is there a mechanism to get at the profile here that I am not seeing? Perhaps using the passed in 'code' parameter to lookup the profile from the ticket registry? Thanks in advance for any help troubleshooting this! -- - 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/1b25d783-0790-4913-8f7f-757a645d7e30%40apereo.org.
