add support for OAuth state variable #81
Merged
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 of change:
MailChimp is removing support for wild card
redirect_uris. Per their recent email, copied below, OAuth developers will no longer be able to use fuzzy matching on the redirect uri, and will be required to use astateparameter to pass any state needed for user or route specific info.This change is to add support for a
stateparameter to the OAuth url.Description of implementation:
Added a
stateargument to theMailchimp->getAuthUrl()function, and used it to append astateparameter to theauthUrl. To keep the API backward compatible, thestateparameter is not required, and defaults tonull.Risks & Mitigation:
Backward compatibility with the API, but this addressed by making the added argument not required, and by giving it a default value.