Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add token service auth #489

Open
labkode opened this issue Feb 3, 2020 · 0 comments
Open

Add token service auth #489

labkode opened this issue Feb 3, 2020 · 0 comments

Comments

@labkode
Copy link
Member

labkode commented Feb 3, 2020 •
edited
Loading

Add a new authenticate strategy for Reva to impersonate users based on a trusted service key.

Needed for example when front-end services perform authentication that cannot be handled in Reva itself, like SAML.

So when the user follows the SAML logic, the username will be obtained and will be send to Reva alike:

Authenticate(ctx, "service-key", "secretkey", "username")

Maybe even an AuthenticateWithKey would be better.

Google uses service accounts for machine authentication, maybe that is the model to go ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@labkode