You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2019. It is now read-only.
The reason this is happening is that the script for registering clients in this repo is not registering the client with an id_token tokenresponse_type and an implicitgrant_type, which are necessary per the OIDC specification to use id_token token as a response_type. Prior, Anvil Connect did not validate this part of the client metadata, but now it is compliant with the standard, and does.
There's another problem, and that is that the implicitgrant_type does not allow the registered client to use http; only https or a custom scheme is allowed. We only enforce this particular aspect in a production environment, but if Anvil Connect is running inside Docker, it is always running with NODE_ENV set to production, and thus clients using the implicit auth flow must be using SSL.
Therefore, in order to work, this project should:
Register the client with the correct response_type and grant_type claims
Run with SSL
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the example with popup, clicking signin gives this in the console for
callback_popup.html
:pageUrl=http://localhost:9000/callback_popup.html#error=unsupported_response_type&error_description=Unsupported%20response%20type
The
response_type
is not specified in the demo app, the default fromanvil-connect
appears to be'id_token token'
The text was updated successfully, but these errors were encountered: