No longer able to get ID Token on non-OIDC client

Our non OIDC client has been working fine until one day ago (March 13, 2018).

We used to be able obtain the ID Token from the response by specifying response_type=token. For scope we are including “openid” among other things.

Since yesterday, the response is too long for our application and does not include the ID Token.

Specifying response_type=id_token token seems to fix the issue (although this results in a state string mismatch). We do not have “OIDC Conformant” enabled on this client.

We were not expecting this behavior to suddenly change without notice! Our software is deployed in a .NET desktop application, so our customers will no longer be able to log in with their current software. Is there anything that can be done to bring back the old behavior?

Hey @amh

As it has been more than a few months since this topic was opened and there has been no reply or further information provided from the community as to the existence of the issue we would like to check if you are still facing the described challenge?

We are more than happy to assist in any way! If the issue is still out there please let us know so we can create a new thread for better visibility, otherwise we’ll close this one in week’s time.

Thank you!

This topic was automatically closed after 6 days. New replies are no longer allowed.