- When setting up an auth provider the config is tested and the user validates against said provider
- We then fetch the principals to find the authenticated user and save it in the auth config
- If however the config is updated by the backend as part of the test process we save a stale version overwriting those changes
- So ensure we reload the resource before proceeding
- url part of `management/find` was incorrect
- url was never used as we normally have the resource, however there's some kind of log in bug #3160 where settings are missing, including server-url
- so server-url was never fetched... dodgy url threw exception... model was never fetched
- we don't have a pattern for $fetchState.error anywhere, which we could use here when fetch failed instead of continueing
- addresses #3137
- When enabling oidc the principal tagged with me should be added to the providers `allowedPrincipalIds` collection
- This wasn't happenening due to a code change (`me` --> `principal`)
- Much of the grunt work is generic OIDC
Also fixed
- store's principalId was not updated after user enables any auth provider
- Colour of InfoBox title in dark mode
- Issue where some kind of errors when enabling provider were shown as an empty box (exceptionToErrorsArray is now used, which also uses a better catch all stringify)
- An issue where enabling and disabling a provider in the same visit meant lost defaults
- An issue where Auth / Groups would not display (async part had been removed)
- Resource instance validation would show all fields as invalid once one field had failed
Cody Jackson
Richard Cox
Nancy Butler
Neil MacDougall
Neil MacDougall
Cody Jackson