Error when using with Authelia

[dacrudg]

Hi. I'm using this plugin to connect Wordpress to Authelia. Here is a screenshot of what values it wants. What do I set for Login Endpoint, Userinfo Endpoint, etc. ?

I think I may have the values correct. And got this after trying to login:

ERROR (invalid_client): Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). The request was determined to be using 'token_endpoint_auth_method' method 'client_secret_post', however the OAuth 2.0 client registration does not allow this method.

[timnolte]

So per the documentation I found you should have the standard Well Known Discovery Endpoint available that should provide you all of the details needed to configure the plugin.

https://www.authelia.com/integration/openid-connect/introduction/#well-known-discovery-endpoints

[timnolte]

@dac11011 were you able to get things working?

[Glowsome]

@timnolte (imho) it would be a huge upgrade/enhancement if the plugin was able to accept (as a switch) either the well-known-configuration endpoint and iterate it on its own, or accept manual input(per needed/required endpoint) for config.

This would make (again imho) configuration of the plugin alot easyer.

• Glowsome

[timnolte]

@Glowsome this has been asked, and something that I agree would help with some of the configuration, though there are a number of settings that can differ depending on user preferences. In this case though they didn't even know about the endpoint.

I don't believe there is any automated way to find the endpoint without it being supplied. So for those that don't know how to find this it will still do little to resolve this issue. I even had a hard time tracking down documentation for this IDP on anything about the .well-known endpoint. I find it odd that IDPs don't actually push this as the recommended way to configure clients. 🤷‍♂️

[Glowsome]

@Glowsome this has been asked, and something that I agree would help with some of the configuration, though there are a number of settings that can differ depending on user preferences. In this case though they didn't even know about the endpoint.

I don't believe there is any automated way to find the endpoint without it being supplied. So for those that don't know how to find this it will still do little to resolve this issue. I even had a hard time tracking down documentation for this IDP on anything about the .well-known endpoint. I find it odd that IDPs don't actually push this as the recommended way to configure clients. 🤷‍♂️

Not asking for a 'push' more like an option if there is a well-known - endpoint avail ( as said an option).

From my (in use IDP) i know it supports/has a well-known endpoint In this i (maybe mistakenly) assumed that this was by default available on all

• Glowsome

[timnolte]

@Glowsome so, I'm pretty certain that all OpenID Connect compliant IDPs are required to support the well-known endpoint, however they all implement it with an unknown path, and often I've found it a challenge to track down the endpoint URLs. Like I said though I do agree it would be a good addition to simplify setup for folks that know about it, and have it.

I'll try to see about making this a priority soon. https://github.com/oidc-wp/openid-connect-generic/issues/248

[rmaziere]

Hello @dac11011, Did you succeed to configure ?