[
https://issues.apache.org/jira/browse/CASSANDRA-21546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105536#comment-18105536
]
Stefan Miklosovic commented on CASSANDRA-21546:
-----------------------------------------------
great final touch, [~frankgh]!
I think the only thing which is missing is to add this new feature into
NEWS.txt, I think it is interesting / important enough that a new entry there
is justified. I would also like to see added documentation on the website,
somewhere around here (1), mentioning this is possible etc. Just to give some
brief how-to for readers. If they do not consult cassandra.yaml they will not
know this exists, I think we should advertise what we are doing more.
I will take care of CI and merge once addressed.
(1)
https://cassandra.apache.org/doc/latest/cassandra/managing/operating/security.html#operation-roles
> Support pluggable default role initialization (avoid hardcoded superuser
> password)
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-21546
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21546
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Feature/Authentication
> Reporter: Aparna Naik
> Assignee: Aparna Naik
> Priority: Normal
> Fix For: 7.x
>
> Attachments: ci_summary.html, result_details.tar.gz
>
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> Cassandra's first-boot bootstrap hardcodes the creation of a cassandra
> superuser role with a default password (cassandra). Every new cluster starts
> with this guessable credential exposed until an operator manually rotates or
> drops it, and deployments that already use mutual TLS have no way to
> bootstrap a superuser identity without also creating this password-based one.
> This ticket will make the default role bootstrap pluggable via a new
> IDefaultRoleInitializer interface and default_role_initializer config option.
> The existing password-based behavior will be the default implementation for
> backward compatibility, and it will add a MutualTlsDefaultRoleInitializer
> that instead maps a client certificate identity to the superuser role, so no
> password credential needs to exist at all.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]