Issue 1
Cant login to the Dashbaord UI in localhost. OS: CentOS 9
Why this issue to fixed / feature is needed(give scenarios or use cases):
Cant login with the credentials in the dashboard after running sudo -E env "PATH=$PATH" ansible-playbook site.yml -i local.hosts -vvv --tags dashboard , Soda Dashboard: https://{hostip}:8088
Other Notes / Environment Information: (Please give the anv information, log link or any useful information for this issue)
Note did not have any error after running the above command.
Issue 2
If the SODA Dashboard is left idle for a while, the authentication token gets expired in the keystone backend but the dashboard does not reflect the same. It remains active and allows user to perform actions for ex: create bucket, create profile etc.
On clicking the create button the API throws a 403 unauthorised error due to the token not being valid.
Issue 3
Issue/Feature Description:
Dashboard remains ideal even after session timeout. This leads to failure for all http requests
Why this issue to fixed / feature is needed(give scenarios or use cases):
Issue 1 Cant login to the Dashbaord UI in localhost. OS: CentOS 9
Why this issue to fixed / feature is needed(give scenarios or use cases): Cant login with the credentials in the dashboard after running sudo -E env "PATH=$PATH" ansible-playbook site.yml -i local.hosts -vvv --tags dashboard , Soda Dashboard: https://{hostip}:8088
Other Notes / Environment Information: (Please give the anv information, log link or any useful information for this issue) Note did not have any error after running the above command.
Issue 2 If the SODA Dashboard is left idle for a while, the authentication token gets expired in the keystone backend but the dashboard does not reflect the same. It remains active and allows user to perform actions for ex: create bucket, create profile etc. On clicking the create button the API throws a 403 unauthorised error due to the token not being valid.
Issue 3 Issue/Feature Description:
Dashboard remains ideal even after session timeout. This leads to failure for all http requests
Why this issue to fixed / feature is needed(give scenarios or use cases):
User need to be aware of session time out.