docs: add OnPay to the third-party provider clients - #1119
Open
tomsommer wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds OnPay to the third-party provider clients list.
league/oauth2-client ^2.8, PHP 8.2+OnPay is a Danish payment gateway. The provider supports the authorization code and refresh token grants, optional PKCE, and an optional gateway id that scopes the authorization endpoint to a single gateway.
Two notes in case they matter to anyone reviewing: OnPay issues public clients only, so there is no client secret, and it exposes no resource owner endpoint (an access token authorizes a gateway rather than a person), so
getResourceOwner()andgetResourceOwnerDetailsUrl()throwBadMethodCallExceptionand noACCESS_TOKEN_RESOURCE_OWNER_IDis set. Both are documented in the package README.The row is inserted alphabetically between Okta and OpenStreetMap.