-
Notifications
You must be signed in to change notification settings - Fork 406
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
Retrieving oAuth token fails every time on first call #8914
Comments
@jakkab please provide more details here what happened, why we have updated version etc and close it ;) |
Please refer to ory/hydra#1599. It looks like switching the db driver from lib/pq to jackc/pgx in Hydra solves the problem. Moreover, we might want to set For now, Hydra has been bumped to v1.4.6 (#9016). This version features updated drivers. |
The issue persists, we need to investigate further. |
@yarivlifchuk #9317 should stabilize the connection. Feel free to reopen in case the issue persists. |
Thanks |
Happened again: kyma-integration-gardener-aws |
See also: #10965 |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
The test is replaced by fast-integration tests. |
Description
Kyma version 1.11.1
When calling the following curl to retrieve token there is a failure response and only in the 2nd call it succeed with new token.
Expected result
Get success response on first shot.
300{"access_token":"hbhwWJDunwBFlEAWJjHiqK3CvrICJ8dt7g-VMGI7TmI.yHg41WlnOOPzzm64cmscope":"application:read","token_type":"bearer"}
Actual result
a failure response in the 1st attempt and only in the 2nd call it succeed with new token.
Steps to reproduce
Call the following URL (replace clientId,clientSecret and Kyma domain)
Troubleshooting
Calling it several times until succeed response
The text was updated successfully, but these errors were encountered: