-
Notifications
You must be signed in to change notification settings - Fork 18
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
add support for appRole authentication #251
Labels
area/auth
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/keep
Denotes an issue or PR that should be preserved from going stale.
Comments
josueCarvajal
changed the title
appRole authentication is producing this error
appRole authentication not working as expected
Dec 5, 2023
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Feb 4, 2024
We currently don't support it, but we definitely should have this in place as well. Will add to backlog for future implementations, but we don't really have a deadline on when we can start working on this. |
ramizpolic
changed the title
appRole authentication not working as expected
add support for appRole authentication
Feb 9, 2024
ramizpolic
added
area/auth
kind/feature
Categorizes issue or PR as related to a new feature.
and removed
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
labels
Feb 9, 2024
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Apr 14, 2024
csatib02
removed
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Apr 14, 2024
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Jun 16, 2024
csatib02
removed
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Jun 16, 2024
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Aug 18, 2024
csatib02
added
lifecycle/keep
Denotes an issue or PR that should be preserved from going stale.
and removed
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
labels
Aug 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/auth
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/keep
Denotes an issue or PR that should be preserved from going stale.
Problem statement
Due to business requirements we want to move away from kubernetes auth to use appRole authentication.
So far, the implementation goes well with hashicorp vault and tools consuming an approle and using the hashicorp agent injector,
but when trying to use the BanzaiCloud webhook we are facing a limitation with the banzai webhook that might make us re-plan our strategy of moving to this method.
Scenario details
These are our annotations for the banzai webhook
and the error we are getting is the following:
By digging around I was able to logIn via CLI using the following post resquest
But when using the following post request, using role_name instead of role_id
I get the same error, meaning that the webhook is building the post request in the same way
Also I was looking at this annotation
vault.security.banzaicloud.io/token-auth-mount
but not sure how it works, when I've enabled it as a volume mount with the token the webhook is not injected, if this is a missing piece in this puzzle could you please guide me through an example in how to use it?Versions used:
Questions
Thanks in advance!
The text was updated successfully, but these errors were encountered: