Closed elsopapa closed 3 years ago
Is this log from the k8s install or from your other instance?
from the k8s install
I don't see errors in that log. What problem are you experiencing?
the problem is In the standard vm installation (same version and config but without k8s) the role assigment works ok . In the k8s install i can login but i dont have any role asigned .
Try something like this:
config: |
...
- #[rbac]
- # enable = True
- #backend = ldap
- #sync_remote_groups = True
+ [rbac]
+ sync_remote_groups = True
...
rbac:
enabled: true
- backend: ldap
- sync_remote_groups: true
Why: Specific rbac settings go in the config section. But the chart needs to know if rbac is enabled, so that setting is managed in its own spot. Also the rbac backend is always "default" -- only auth can work with ldap. Plus the chart automatically sets the rbac backend when rbac is enabled, so you don't need to do that.
I already did that test , and it doesnt work. i will try again.
Solved, the problem was a casesentive configuration in the group's name ( works in the standar installation but not in k8s).
I have a problem in the role assigment when i use ldap as auth backend I have a test site with a standard instalation ,( without kubernetes, and the conf works well and take the roles )