welknown and supported response types

[pniederlag]

I tried to use mock-oauth2-server as "provider" for automated testing of an apache-setup with https://github.com/OpenIDC/mod_auth_openidc/tree/master

Would this be a valid use-case for mock-oauth2-server?

Currently I am stuck at the apache module logging this error:

auth_openidc:error oidc_metadata_provider_is_valid: could not find a supported response type in provider metadata ((null)) for entry "response_types_supported"

The json from the wellknown-endpoint is received, but mod_auth_openidc seems to miss some piece... :-<

[pniederlag]

Digging further into .well-known and openid-configuration options I discover there are two properties

response_modes_supported and response_types_supported

https://github.com/OpenIDC/mod_auth_openidc/blob/master/auth_openidc.conf

Digging through some public openidc endpoints it seems 'response_types_support' and 'response_modes_supported' yield:

 curl -sS https://sso.redhat.com/auth/realms/redhat-external/.well-known/openid-configuration | jq '.response_types_supported, .response_modes_supported'
[
  "code",
  "none",
  "id_token",
  "token",
  "id_token token",
  "code id_token",
  "code token",
  "code id_token token"
]
[
  "query",
  "fragment",
  "form_post",
  "query.jwt",
  "fragment.jwt",
  "form_post.jwt",
  "jwt"
]

So I assume the well-known endpoint should probably be configured in a similar way?