You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
Project board link
Even though the configured variable for shiro.ini is effectively used as a config when set:
cassandra-reaper/src/server/src/main/docker/configure-webui-authentication.sh
Lines 20 to 26 in 92ddde6
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.cassandra-reaper/src/server/src/main/docker/configure-webui-authentication.sh
Lines 43 to 47 in 92ddde6
Maybe not a bug per se, but it makes intent ambiguous regarding the purpose of the
REAPER_AUTH_USER
variable whenREAPER_SHIRO_INI
is set to a non-default value.┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: REAP-6
The text was updated successfully, but these errors were encountered: