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
Hitting "Logout" in DokuWiki in the context of oauth may result in two actions:
remove the application session from the IdP => this will somewhat disconnect the service, but as soon as the user accesses an URL of DokuWiki he is logged in again.
destroy the user session in the IdP => this will logout the user from the IdP, but not only for the use of DokuWiki but of all logged-in applications (SSO).
If there is a logout-button, a user might click on it, but he has no clue what happens next. If he click, reload the page and is just in again, he get the impression that the button has no use. On the other side if he click and get's logged out of all other services which he is using in parallel, he will be surprised also.
Both scenarios are complicated to handle and i think about if there should be a logout-button at all, or if the button should redirect to the IdP account page, where a user can logout, if he want to?
The text was updated successfully, but these errors were encountered:
Hitting "Logout" in DokuWiki in the context of oauth may result in two actions:
If there is a logout-button, a user might click on it, but he has no clue what happens next. If he click, reload the page and is just in again, he get the impression that the button has no use. On the other side if he click and get's logged out of all other services which he is using in parallel, he will be surprised also.
Both scenarios are complicated to handle and i think about if there should be a logout-button at all, or if the button should redirect to the IdP account page, where a user can logout, if he want to?
The text was updated successfully, but these errors were encountered: