Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 44 Oracle Analytics and AI Sharing Center
- 20 Oracle Analytics and AI Lounge
- 278 Oracle Analytics and AI News
- 56 Oracle Analytics and AI Videos
- 16.2K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 103 Oracle Analytics and AI Trainings
- 20 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Handling user ID in FDI post P2T refresh
In a production to test environment refresh process if a user's id does not exist in production instance, how will the user would be able to login to FDI post refresh who was earlier a service administrator.
will the access need to recreated in lower ERP instance or we can primarily mitigate this issue by following some other approach.
Answers
-
@User_7AIAG , this is a very good question and there are few options to mitigate this situation.
Option 1: Recreate the user and roles in the lower environment
After the refresh, you manually re-create the user in the test environment and assign them the Service Administrator role again. This is usually the standard approach for non-production-only users.
Option 2: Pre-refresh preparation
- Export a list of test-only users and their roles before the refresh and after the refresh, re-import or recreate these users with their roles.
- Option 3: Use an identity federation / SSO
If FDI is integrated with SSO (e.g., OCI Identity, IDCS), the user can exist in the identity provider, even if they are not in production. You would still need to assign FDI roles after refresh, but login can work if the ID exists in IDCS.
Hope it helps!
0
