* wip
* add logout action according to logic (SAML - logoutAll) + add modal to prompt user to select SLO logout type when logging out of Dashboard
* update authProvidersInfo method to allow for a getter usage in order to make it store reactive
* wip - missing final plumbing for the finalRedirectUrl
* bug fix for non-reactive header logout when auth provider is enabled
* adjust slo UI elements to match expected UI/UX
* minor adjustments + pr cleanup
* cleanup
* handle promise rejection for standard users (apparently they cannot get the schema)
* Updates
- Tweaked text (to be reviewed)
- Removed some code smells
- Ensure rancher logout via modal uses same process as normal logout
- Use async buttons in logout modal
- Add cancel to log out modal
- Fix logout on fail-whale page
* Add error handling (WIP with Andreas, does not currently reach final redirct / verify route)
* Fix check for IS_SLO
* Only allow optional auth provider log out if logged in auth provider
* Fix error message (SLO failures still result in rancher log out)
* check complete slo flow + add special copy when doing a slo logout
* Update shell/dialog/SloDialog.vue
Co-authored-by: Phillip Rak <rak.phillip@gmail.com>
* Update shell/edit/auth/saml.vue
Co-authored-by: Phillip Rak <rak.phillip@gmail.com>
* update syntax from phil pr review
* Fix logout modal on diangostics, about, etc pages that use plain template
* Remove PromptRemove from diagnostic page
- it uses the plain template which now contains it
- caused x2 modals to show
---------
Co-authored-by: Richard Cox <richard.cox@suse.com>
Co-authored-by: Phillip Rak <rak.phillip@gmail.com>
- Follows on from
- https://github.com/rancher/dashboard/pull/6603
- https://github.com/rancher/dashboard/pull/6700
- To track messages the console methods were overwritten
- When the console methods were called, we would track message and then call the original console method
- Output into the standard browser console window was broken though
- the inline stack trace for all logs is the place where the original console method is called
- this was always `console.js`
- This causes issues whilst in development but also for logs coming from customers
- Investigate ways around this, but couldn't find anything nice
- short term solution is to remove the feature
* Prevent ESLint to format generated paths
* Add HTML ESLint Rules
* Format all the Vue HTML templates except Harvester
* Exclude Harvester package from linting HTML, keeping old formatting rules
- The download diagnostics button would clean the store before saving
- The issue was it was cleaning the actual store, resulting in all resources being lost
- We now flip the logic to save allowed properties to a new object, so the original store should be untouched