-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for AuthEvent in OAuth2 Flow #13
Comments
Hi @rjhankison I had been trying to understand what needs to be done to effect a solution for your question as I too had an issue with this. Today I solved that problem.
This will get you what you want. It is only useful when the first Access Token is retrieved as the 'authentication_event_id' changes with each refresh so you must store the Tenant ID somewhere as you would the Access Token. As for as how this should be implemented I would assume it would make sense to implement a solution to this upstream in the Thanks |
Thanks Gary! Yes, we found a similar solution:
We also noticed the same constraint around a the Anyway, it makes me feel better knowing that you've come to the same conclusion. :) Thanks again! |
Hi all, sorry I completely missed this thread! Would you like a method like that added to the library? I'm happy to take a PR if you've done something to resolve it locally. |
Hi there -- first off, thank you so much for building this library! Our team loves working with it. :-D
We're running into an issue where our application cannot tell which organization a user authenticates in the OAuth2 flow. This occurs when a user has multiple connections to our application. We're missing a way to examine the JWT for an AuthEventID. We can use that ID to determine which organization a user authorized in that handshake. However, I don't see a way to examine this event in your library. Here's the response I received from Xero support for context:
Do you have plans to include a method for this on your Calcinai\OAuth2\Client\Provider\Xero class?
Thanks so much in advance!
The text was updated successfully, but these errors were encountered: