-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Added E2E Test: Client Credentials with Certificate from Key Vault #7367
Conversation
...ntials-with-cert-from-key-vault/test/client-credentials-with-cert-from-key-vault-aad.spec.ts
Show resolved
Hide resolved
...ntials-with-cert-from-key-vault/test/client-credentials-with-cert-from-key-vault-aad.spec.ts
Show resolved
Hide resolved
...ntials-with-cert-from-key-vault/test/client-credentials-with-cert-from-key-vault-aad.spec.ts
Show resolved
Hide resolved
...ntials-with-cert-from-key-vault/test/client-credentials-with-cert-from-key-vault-aad.spec.ts
Show resolved
Hide resolved
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.
See if you can also test the cached tokens. Maybe even expire them and try to acquire new ones if that is possible.
This is all handled in the unit tests. We just want to verify the token is received from the network request (via cert auth) here. |
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 would strongly recommend also testing caching operations in integration tests. But it is not mandatory
This was meant to be included in #7367. [Corresponding 1P PR](https://identitydivision.visualstudio.com/DefaultCollection/IDDP/_git/msal-javascript-1p/pullrequest/15266) You can click into the tests below and see that the new e2e tests completed successfully.
This PR adds a sample with a corresponding e2e test.
A follow up PR that converts the sample to TypeScript is located here.
Additionally, some potential follow up work would be to re-use some of the certificate transforming functionality introduced here and change the way developers pass in certificates.