Skip to content
This repository has been archived by the owner on Feb 25, 2019. It is now read-only.

unsupported_response_type #7

Open
ikb42 opened this issue Sep 28, 2015 · 1 comment
Open

unsupported_response_type #7

ikb42 opened this issue Sep 28, 2015 · 1 comment
Labels

Comments

@ikb42
Copy link
Contributor

ikb42 commented Sep 28, 2015

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 from anvil-connect appears to be 'id_token token'

@adalinesimonian
Copy link
Member

The reason this is happening is that the script for registering clients in this repo is not registering the client with an id_token token response_type and an implicit grant_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 implicit grant_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:

  1. Register the client with the correct response_type and grant_type claims
  2. Run with SSL

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants