You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the vault binary, it's super easy to get a human user OIDC authed to Vault. They declare their role name, the vault client bounces up a web browser to get or check their auth status against the idP, and away you go.
The VaultSharp library, by contrast, is expecting a role name and a JWT. I don't see any example code on how one might generate a JWT (when you're authing with OIDC specifically). I do see the Non Login methods in IJWTAuthMethod.cs
but I'm unclear on how to use them, or if the "OIDC ID Token" returned by DoOIDCCallbackAsync is the same thing as a JWT token in the first place.
I don't see anything at all on github that shows someone using these methods in their own code, so I'm having a tough time answering this on my own.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Using the vault binary, it's super easy to get a human user OIDC authed to Vault. They declare their role name, the vault client bounces up a web browser to get or check their auth status against the idP, and away you go.
The VaultSharp library, by contrast, is expecting a role name and a JWT. I don't see any example code on how one might generate a JWT (when you're authing with OIDC specifically). I do see the Non Login methods in IJWTAuthMethod.cs
but I'm unclear on how to use them, or if the "OIDC ID Token" returned by DoOIDCCallbackAsync is the same thing as a JWT token in the first place.
I don't see anything at all on github that shows someone using these methods in their own code, so I'm having a tough time answering this on my own.
Beta Was this translation helpful? Give feedback.
All reactions