[
https://issues.apache.org/jira/browse/CASSANDRA-19946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago L. Alves updated CASSANDRA-19946:
---------------------------------------
Description:
The implementation of custom authentication / authorization can be achieved by
implementing {{{}IAuthenticator{}}}, {{{}IAuthorizer{}}}, {{{}IRoleManager{}}},
and other interfaces.
{{IAuthenticator}} implementations, for instance, can additionally read extra
configuration parameters via a map of strings defined in
{{{}cassandra.yaml{}}}. This enables an user to conveniently define and
configure it's own Authenticator directly in {{{}cassandra.yaml{}}}.
This configuration mechanism is currently enabled for {{Authenticator}} and
{{CIDRAuthorizer}} implementations only but not for {{{}Authorizer{}}},
{{{}RoleManager{}}}, and {{{}NetworkAuthorizer{}}}.
To enable an user to set and configure custom authentication/authorization we
should enable the same parameter options for all {{{}Authorizer{}}},
{{{}RoleManager{}}}, and {{NetworkAuthorizer}} implementations. This can be
achieved by enabling all those implementations via {{{}ParameterizedClass{}}}.
From an user point of view, configuring existent authenticators/authorizators
will have no visible changes.
was:
The implementation of custom authentication / authorization can be achieved by
implementing {{{}IAuthenticator{}}}, {{{}IAuthorizer{}}}, {{{}IRoleManager{}}},
and other interfaces.
{{IAuthenticator}} implementations, for instance, can additionally read extra
configuration parameters via a map of strings defined in
{{{}cassandra.yaml{}}}. This enables an user to conveniently define and
configure it's own Authenticator directly in {{{}cassandra.yaml{}}}.
This configuration mechanism is currently enabled for {{Authenticator}} and
{{CIDRAuthorizer}} implementations only but not for {{{}Authorizer{}}},
{{{}RoleManager{}}}, and {{{}NetworkAuthorizer{}}}.
To enable an user to set and configure custom authentication/authorization we
should enable the same parameter options for all {{{}Authorizer{}}},
{{{}RoleManager{}}}, and {{NetworkAuthorizer}} implementations.
> Allow configuration parameters for IAuthorizer, INetworkAuthorizer, and
> IRoleManager
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19946
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19946
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Tiago L. Alves
> Priority: Normal
>
> The implementation of custom authentication / authorization can be achieved
> by implementing {{{}IAuthenticator{}}}, {{{}IAuthorizer{}}},
> {{{}IRoleManager{}}}, and other interfaces.
> {{IAuthenticator}} implementations, for instance, can additionally read extra
> configuration parameters via a map of strings defined in
> {{{}cassandra.yaml{}}}. This enables an user to conveniently define and
> configure it's own Authenticator directly in {{{}cassandra.yaml{}}}.
> This configuration mechanism is currently enabled for {{Authenticator}} and
> {{CIDRAuthorizer}} implementations only but not for {{{}Authorizer{}}},
> {{{}RoleManager{}}}, and {{{}NetworkAuthorizer{}}}.
> To enable an user to set and configure custom authentication/authorization we
> should enable the same parameter options for all {{{}Authorizer{}}},
> {{{}RoleManager{}}}, and {{NetworkAuthorizer}} implementations. This can be
> achieved by enabling all those implementations via
> {{{}ParameterizedClass{}}}. From an user point of view, configuring existent
> authenticators/authorizators will have no visible changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
