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
Using Stratos-2.0.0-rc3 with Chromium Version 66.0.3359.170 (openSUSE Build) (64-bit)
Backend (portal-proxy) Deployment type
Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please specify below)
Expected behaviour
Logout removes the session cockie and redirects to login page.
(there's only one session-cookie)
Actual behaviour
Logout brings you back, to the current page - staying logged in.
((This does only happen, if you've reused the open browser session from version A on version B after an upgrade))
Steps to reproduce the behavior
Install Stratos-1.1.0, e.g. suse/console, console-1.1.0
Login to Stratos Console
helm upgrade to Stratos-2.0.0-rc3 and wait for the UI to be available for sure
(e.g. helm upgrade --recreate-pods console helm/console --values scf-config-values.yaml)
Return to your browser to reuse the open session (e.g. by reloading)
When your session is still valid and you are provided with the 2.0.0 UI, try to log out
=> logout will not be possible, until one deletes the session cookies manually
The text was updated successfully, but these errors were encountered:
Frontent Deployment type
Using Stratos-2.0.0-rc3 with Chromium Version 66.0.3359.170 (openSUSE Build) (64-bit)
Backend (portal-proxy) Deployment type
Expected behaviour
Logout removes the session cockie and redirects to login page.
(there's only one session-cookie)
Actual behaviour
Logout brings you back, to the current page - staying logged in.
((This does only happen, if you've reused the open browser session from version A on version B after an upgrade))
Steps to reproduce the behavior
(e.g.
helm upgrade --recreate-pods console helm/console --values scf-config-values.yaml
)=> logout will not be possible, until one deletes the session cookies manually
The text was updated successfully, but these errors were encountered: