-
Notifications
You must be signed in to change notification settings - Fork 329
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
Howto integrate Vouch Proxy into a server side application for User Identification, Authentication and Authorization #421
Comments
@mamcx VP does not replace Auth0 or Keycloak, it piggybacks on Authentication/login at those IdPs to provide Authorization / gatekeeper services. Does that make sense? In addition some of the information provided by the IdP (Auth0, Keycloak, Google, ...) can be handed to an underlying web application as HTTP headers. If there were any improvement to the README which would help to clarify that could you please suggest such. |
So, if I wanna get close to them, what exactly do I need to provide? For the link I put above, I need to validate the login myself and provide routes/UI, but I don't know if that is enough or exist some more steps. So it will be nice to have a tutorial that implements a solution end-to-end. |
@mamcx for posterity could you outline what you're trying to do in a bit clearer terms? I'm a little unclear on your architecture. When you say
it makes me think that you'd be fine with just doing as the README outlines and put your app behind Nginx with
Could you please clarify what you're wanting here |
@mamcx if you're no longer working this issue could you please close it |
I mean, how and if this software is close to having Auth0 and how to make it so. I think what is not clear is the high-level example like "add auth to you API/blog/whatever" and see what extra steps I need to complete to connect to my backend/tables. For example: https://auth0.com/blog/build-an-api-in-rust-with-jwt-authentication-using-actix-web/ |
@mamcx unfortunately that isn't documented but it's pretty simple... The
And these headers for
Those headers would need to be passed to your app in an Nginx
And then you would build logic into your app to key off the user, or forward back to However, to be clear, VP does not provide it's own store of user information. You would need to use an |
related: #432 |
@mamcx does that clarify things for you? If you have no further questions would you please close the issue. |
I'm looking for a way to secure my tenants APIs/Web Stores and want something that allow me to use my own tables/bussines logic but offload security elsewhere. A obvious choice is to use Auth0/Keycloak or something similar, but that provide challenging integration issues with my customers/apps (I'm in the enterprise sector).
Is this project something I can put on front of my apps/sites and gives a good security for it? I need to complement this with something else?
P.D: I'm aware I will need to code things like #359, this is what actually attract me to the idea of use this...
The text was updated successfully, but these errors were encountered: