[satosa-users] Re: satosa-oidcop and the OIDC Playground

I'm trying to test my SATOSA OIDC OP using the OpenID Connect Playground, but it looks like the client isn't registering itself with SATOSA properly. I don't know how to fix this and would be grateful for any help! I have installed satosa-oidcop (https://github.com/UniversitaDellaCalabria/SATOSA-oidcop) and configured it to use Amazon DocumentDB (MongoDB-compatible). On https://openidconnect.net/: - I select the "OpenID Connect + OAuth2" mode (default and only option). - I click "Configuration". - I select the "Custom" server template. - I enter the discovery document URL generated by SATOSA ($BASE_URL/.well-known/openid-configuration), click "Use Discovery Document", and click "Save". The configuration tool sets the authorization token endpoint to $BASE_URL/Saml2/OIDC/authorization, the token endpoint to $BASE_URL/OIDC/token, and the token keys endpoint to $BASE_URL/OIDC/jwks. This looks correct. The configuration tool tells me to set "https://openidconnect.net/callback" as an allowed callback within my application, and it shows me its OIDC Client ID, OIDC client secret, scopes (defaults to "openid profile email phone address"), and optional audience (blank). When I click "Start" to begin the OIDC authentication process, I get the following error: https://openidconnect.net/callback?error=invalid_request&error_message=…. .. SATOSA logs the following at client configuration time: ``` [DEBUG] [satosa.routing.endpoint_routing] [urn:uuid:..1] Routing path: .well-known/openid-configuration [DEBUG] [satosa.routing.endpoint_routing] [urn:uuid:..1] Unknown backend .well-known [DEBUG] [satosa.routing._find_registered_endpoint_for_module] [urn:uuid:..1] Found registered endpoint: module name:'OIDC', endpoint: .well-known/openid-configuration Then it logs the following when I start the OIDC request process: ``` [ERROR] [pyop.request_validator.response_type_is_in_registered_response_types] client metadata is missing response_types [ERROR] [satosa.frontends.openid_connect._handle_authn_request] [urn:uuid:..2] Error in authn req: Response type is not registered ``` When I look at DocumentDB, I see the "satosa" database and accompanying collections, but the clients collection appears to be empty: ``` rs0:PRIMARY> show dbs sample_database 0.000GB satosa 0.000GB rs0:PRIMARY> use satosa switched to db satosa rs0:PRIMARY> show collections access_tokens authz_codes clients refresh_tokens subject_identifiers rs0:PRIMARY> db.clients.find() rs0:PRIMARY> ``` What am I missing? -- "The reason that ed is the standard editor is to remind you that things could be worse, and once were." -- Tim Lavoie in comp.lang.lisp _______________________________________________ satosa-users mailing list -- satosa-users(a)lists.sunet.se To unsubscribe send an email to satosa-users-leave(a)lists.sunet.se