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
Caching the OAuth tokens in Application Gateway #15924
Conversation
✅ 🥰 Documentation preview ready! 🥰
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, add also the test case for the normal OAuth, mentioned in the issue
crt: {{ $files.Get "certs/invalid-ca/client.crt" | b64enc }} | ||
key: {{ $files.Get "certs/invalid-ca/client.key" | b64enc }} | ||
clientId: {{ "clientID" | b64enc }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in the tests, we can change all the clientIDs from someClientID...
to just clientID
, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we can also change that
crt: {{ $files.Get "certs/invalid-ca/client.crt" | b64enc }} | ||
key: {{ $files.Get "certs/invalid-ca/client.key" | b64enc }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the ...negative...
changed to the ...invalid-ca...
there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same CA signs a positive certificate and a negative certificate. For this test, I generated certificates that are signed by other CA.
@@ -5,5 +5,5 @@ metadata: | |||
namespace: kyma-integration | |||
type: Opaque | |||
data: | |||
clientId: {{ "bad id" | b64enc }} | |||
clientId: {{ "clientID" | b64enc }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this one should not be changed :d It's the oauth-negative-incorrect-id
case
/test pre-main-kyma-integration-k3d |
/test pre-main-kyma-integration-k3d |
Description
Changes proposed in this pull request:
clientID + clientSecret + authURL
clientID + sha256Certificate + sha256Key + authURL
Related issue(s)
For more information visit https://extra.secret.repository/kyma/backlog/issues/2774