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
I am about to create a PR to support this, by allowing the clientSecret parameter to be passed as an object, contains options to be merged with the Wreck request options used when calling the token endpoint.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To allow custom OAuth2 Client authentication, it should be possible to pass client secrets as something else than a password. An example when using PingFederate as custom provider is the ability to use client-certificate-based authentication to authenticate the client with the token endpoint: https://documentation.pingidentity.com/pingfederate/pf81/index.shtml#concept_configuringClient.html
I am about to create a PR to support this, by allowing the clientSecret parameter to be passed as an object, contains options to be merged with the Wreck request options used when calling the token endpoint.
The text was updated successfully, but these errors were encountered: