horizon ui crashed on disabling current domain

[hossein zabolzadeh]

Disabling the currently logged-in domain, renders the horizon UI inoperable. We need either 1- disallow users from disabling(deleting) currently logged-in domains, or 2-handle the error anyway.

How to reproduce?
1- Activate v3 APIs in horizon
2- Login with userA in domainA with edit permision
3- go to identity/domains
4- click on the edit button to edit DomainA
5- disable domainA
6- Several error message shows and the UI freezed in loading state(See the attachement)

Check the attachement.

[David Lyle (david-lyle)]

I think a danger dialog when performing on current domain would be beneficial. Then if the user continues, a logout should be performed.

[Matt Borland (palecrow)]

I agree with David that there should be a better warning mechanism. This might be a good low-hanging-fruit for someone to work on. It seems the operation is inherently dangerous, and an operator should know that, but a reminder and better handling would be best.

[hossein zabolzadeh (zabolzadeh)]

Thanks David and Matt,
Yes I think its better solution to handle it via danger dialog.
I'll submit a patch...

[hossein zabolzadeh (zabolzadeh)]

@Matt,
I checked this bug on horizon (current version) and it resolved properly.
When logged-in user disable currently logged-in domain, then logout performed and 'Unauthorized. Please try logging in again.' message shown on the screen.

So, the state of horizon UI remains stable(as opposed to what explained in bug description).
But informing the user about dangerous of this operation is what needs to be implemented.