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

newUI: admin dashboard lack logoff-button #951

Closed
tvdijen opened this Issue Oct 5, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@tvdijen
Member

tvdijen commented Oct 5, 2018

There is no way to logoff from your admin dashboard.

@tvdijen tvdijen added the help wanted label Oct 5, 2018

@tvdijen tvdijen added this to the 1.17 milestone Oct 5, 2018

@tvdijen tvdijen changed the title from newUI: admin dahsboard lack logoff-button to newUI: admin dashboard lack logoff-button Oct 5, 2018

@thijskh

This comment has been minimized.

Member

thijskh commented Oct 6, 2018

This is also not currently possible in the old ui. While it's a nice feature, not a blocker for 1.17 since not a regression.

@thijskh thijskh removed this from the 1.17 milestone Oct 6, 2018

@thijskh thijskh added the enhancement label Oct 6, 2018

@tvdijen

This comment has been minimized.

Member

tvdijen commented Oct 6, 2018

Well, it's possible when going to 'Test authentication sources' > 'admin', so it would only be a matter of integrating the logout-url on the header-template...
Without arguing your decision to remove the 1.17 milestone, shouldn't this just be a part of any UI nonetheless? And shouldn't we fix the lack of a logoff-link in a new UI if we're working on one?

@thijskh

This comment has been minimized.

Member

thijskh commented Oct 7, 2018

I'm not at all against the idea. It's just not something that should hold back anything because SSP has been without it for years.

@thijskh thijskh closed this in #953 Oct 8, 2018

@thijskh thijskh added this to the 1.17 milestone Oct 8, 2018

@thijskh

This comment has been minimized.

Member

thijskh commented Oct 8, 2018

Indeed better to just fix it instead of discussing priorities :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment