Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
User Story description:
As a user, I want -
Business Rationale:
-
SSO with all my other BC government applications on the standard realm.
Business Rationale:
Reducing the number of logins required will improve the user experience and allow for functionality like embedding forms. Additionally, certain CHEFS API endpoints will become easier to use as the keycloak token generated by a separate application can be used on the CHEFS API endpoints as well, some of which require a keycloak token to function properly.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
Technical Details:
Requires getting rid of custom scopes Configuration
Requires getting rid of custom attribute mappers https://github.com/bcgov/sso-keycloak/wiki/Identity-Provider-Attribute-Mapping
Standard realm does not currently support BCSC login
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 | CHEFS SSO in standard | If a user logs into a different app in the standard realm, the user should not have to log into CHEFS |
2 | Custom realm functionality still works | For teams that still want a custom fork using a custom realm |
3 | Login flow and user management remains the same as before | Nothing should change functionality-wise - just the realm CHEFS is hosted in |
4 |
|
|
5 |
|
|
Prototype/Mockups
Out of Scope:
Contact(s):
Branko Bajic