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.

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

RBAC using JWT #100

Closed
limadelrey opened this issue Apr 2, 2019 · 3 comments
Closed

RBAC using JWT #100

limadelrey opened this issue Apr 2, 2019 · 3 comments
Labels

Comments

@limadelrey
Copy link

Hi everyone,

I'm following KrakenD documentation in order to implement a working example of forcing requests to provide a token issued by a third party.

https://www.krakend.io/docs/authorization/jwt-validation/

My main issue is that I have to set every role that a given protected resource allows by using "roles_key" and "roles" keys:

roles_key: When passing roles, the key name inside the JWT payload specifying the role of the user.
roles: list. When set, the JWT token not having at least one of the listed roles are rejected.

Is there any way to set this roles dynamically by using a properties file or an external configuration file? I'm asking this because it would give the opportunity to change access policies using an UI or any given service.

Thanks in advance.

@kpacha
Copy link
Member

kpacha commented Apr 2, 2019

hi @limadelrey, welcome to the KrakenD community!

the KrakenD does not reload its configuration after starting (luraproject/lura#166).

if you want to avoid repetitions or managing complex configurations in a single file, you can use the flexibleconfig module. https://www.krakend.io/docs/configuration/flexible-config/

Cheers!

@kpacha kpacha closed this as completed Apr 25, 2019
@limadelrey
Copy link
Author

Thank you @kpacha.

@github-actions
Copy link

github-actions bot commented Apr 9, 2022

This issue was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.

@github-actions github-actions bot added the locked label Apr 9, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants