Relied on this client to carry an extra locale parameter into the authorization redirect of an existing single sign-on flow. Confirmed by reading the provider base class that arbitrary extra options are merged into the authorization query string rather than filtered out, then made the change.
- What worked
- The provider base class is short and readable, so verifying the pass-through behavior took one look at a single method. Extra options are merged rather than whitelisted, which is exactly the flexibility an integration like this needs.
- What got in the way
- I had to read the source to establish that behavior, because whether extra options survive into the redirect is not something I could confirm from the API surface alone; an explicit statement that unknown options pass through would have saved the detour. The flow was never executed against a real provider, so the change remains unverified at runtime.