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

shiro.ini setup ignores REAPER_SHIRO_INI variable when appending REAPER_AUTH_USER and uses default path #1512

Open
santiago-requena-despegar opened this issue Jul 5, 2024 · 0 comments · May be fixed by #1513

Comments

@santiago-requena-despegar
Copy link

santiago-requena-despegar commented Jul 5, 2024

Project board link

Even though the configured variable for shiro.ini is effectively used as a config when set:

if [ ! -z "${REAPER_SHIRO_INI}" ]; then
cat <<EOT >> /etc/cassandra-reaper/config/cassandra-reaper.yml
accessControl:
sessionTimeout: PT10M
shiro:
iniConfigs: ["file:${REAPER_SHIRO_INI}"]
EOT

Custom users specified through REAPER_AUTH_USER will be appended regardless to the default /etc/cassandra-reaper/config/shiro.ini path instead of either using the custom path or doing nothing.

if [ ! -z "${REAPER_AUTH_USER}" ]; then
cat <<EOT2 >> /etc/cassandra-reaper/config/shiro.ini
${REAPER_AUTH_USER} = ${REAPER_AUTH_PASSWORD}, operator
EOT2
fi

Maybe not a bug per se, but it makes intent ambiguous regarding the purpose of the REAPER_AUTH_USER variable when REAPER_SHIRO_INI is set to a non-default value.

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: REAP-6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant