Add Client Credentials Flow as Authentication Method #330
Conversation
This file contains 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
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.
Description
Adds the Client Credential Flow as a possible authentication method.
How to use
The Client Credentials flow only requires the consumer secret and key generated by the Salesforce Connected App.
Client Credentials Flowshould also be enabled within Salesforce to allow it to work.You may then set
SF_AUTH_METHODtoClientCredentialsin your .env file, and have the client authenticate directly withForrest::authenticate()Known issues
The PHPSpec file was loosely based on the
UserPasswordspec, which had an issue with theit_should_refresh_the_token_if_token_expired_exception_is_throwntest.