Re: [DISCUSS] Should roles_claim_name be marked as deprecated and replaced in favor of roles_claim_path

2022-10-18 Thread Ronny Berndt
The feature is already included in main and I want to finish and add the documentation for it. Are there any further hints and comments? New PR at: https://github.com/apache/couchdb/pull/4232 Summary: The question is, if we want to deprecate the old setting roles_claim_name and replace it with

Re: [DISCUSS] Should roles_claim_name be marked as deprecated and replaced in favor of roles_claim_path

2022-08-31 Thread Nick Vatamaniuc
If RCPs have all the functionality of RCNs, I think it makes sense to deprecate RCNs. On Tue, Aug 30, 2022 at 9:02 AM Ronny Berndt wrote: > > Overview > > In a JWT token it is possible to add an attribute for role claims. > If the roles are presented as top-level attribute like > > { > "couchdb

[DISCUSS] Should roles_claim_name be marked as deprecated and replaced in favor of roles_claim_path

2022-08-30 Thread Ronny Berndt
Overview In a JWT token it is possible to add an attribute for role claims. If the roles are presented as top-level attribute like { "couchdb-roles": [ "my_role_1", "my_role_2" ] } and setting the parameter roles_claim_name in the config file to [jwt_auth] roles_claim_name = couchd