-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
-
False
-
Unset
-
CRCPLAN-232 - Kessel | PRBAC v2 Service Provider Migration Enablement (Internal)
-
None
-
-
-
5
-
Access & Management Sprint 95, Access & Management Sprint 96
IT will provide a data dump for user data and we'll need a way to repeatably, idempotently run a process to consume this data.
This needs to include the user's ID as part of the export so that we can migrate relations using the user_id and not the username. See RHCLOUD-34770.
This export must be run AFTER RBAC is already syncing user updates in realtime with the newly stored fields (e.g. via UMB). Otherwise we will have a gap in the data.
How to connect to mongodb to retrieve users' data:
https://source.redhat.com/groups/public/gcadba/it_database_service_dba_wiki/how_to_access_to_oracle_mysql_and_mongodb_dbs_for_developers
- blocks
-
RHCLOUD-34859 Migrate existing user relations for default access
-
- Closed
-
- is depended on by
-
RHCLOUD-34770 (User import job) Bootstrap existing Tenants, default group members, and user_id (standard JWT "sub") so access checks work and can use JWTs or identity header without having to use PII or lookup UUID from RBAC
-
- Closed
-
