-
Notifications
You must be signed in to change notification settings - Fork 6
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
Assumed Identity endpoint in Lowkey Vault #960
Comments
Hi @alpapad01 , |
- Adds configuration to listen to the 8080 HTTP port for token requests - Adds new ManagedIdentityTokenController to handle token requests - Adds filter to enforce functional separation between the 8080 and 8443 ports - Extends Testcontainers support with token endpoint related configuration - Adds new tests - Updates documentation Updates #960 {minor} Signed-off-by: Esta Nagy <nagyesta@gmail.com>
- Adds configuration to listen to the 8080 HTTP port for token requests - Adds new ManagedIdentityTokenController to handle token requests - Adds filter to enforce functional separation between the 8080 and 8443 ports - Extends Testcontainers support with token endpoint related configuration - Adds new tests - Updates documentation Updates #960 {minor} Signed-off-by: Esta Nagy <nagyesta@gmail.com>
Hi @alpapad01 , I think it should be working, but please let me know whether it is what you had in mind! Thank you in advance! |
Hi @alpapad01 , Thank you and best of luck! |
Fist, great project, solves a tone of problems. A big thank-you!!
Is your feature request related to a problem? Please describe.
To test an application which uses Azure vault, without changing configurations (and possibly code?), one needs to have the nagyesta/assumed-identity:1.2.16 docker image running next to lowkey-vault.
Describe the solution you'd like
It would be great to expose the single GET endpoint of assumed-identity from lowkey-vault itself. This way, there is one container less to run (less resources).
I have tested such a solution and it works.
The text was updated successfully, but these errors were encountered: