-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Remove redundant call to _authenticate
API after access token is created
#80952
Comments
Pinging @elastic/kibana-security (Team:Security) |
Let me try to work on this issue. |
Hello, @azasypkin! |
Let's take a Token provider as an example, the response for this call already includes all required user information (see I'd suggest you to call these APIs manually and see what they return, I believe it should make clearer where you can eliminate unnecessary calls. |
Hey @gorogoroumaru , I'm going to pick this issue up soon since it's an improvement we'd like to include in the next minor release. But let me know if you're already working on it and planning to come up with a PR any time soon. If you don't have time or interest anymore, that's totally fine, feel free to observe the linked the PR then. That can be useful for you anyway if you're going to contribute to Kibana in the future. |
I’m sorry @azasypkin. |
Since elastic/elasticsearch#59685 is resolved now (7.11.0+) we can proceed and remove redundant
_authenticate
calls after we create any kind of access token (Token/SAML/OIDC/Kerberos/PKI) that would improve login performance and make code simpler overall.The text was updated successfully, but these errors were encountered: