To avoid creating Fusion Application users and their job roles in FDI, which option should you implement?

To avoid creating Fusion Application users and their job roles in FDI, which option should you implement?

• A. Implement SSO and the synchronization of users and job roles between FDI and Fusion Applications before provisioning the FDI instance.
• B. Manually import all users into FDI after provisioning.
• C. Disable SSO to avoid conflicts.
• D. Use a separate identity service for provisioning.

Answer: (A)

Centralized identity management through Single Sign-On and synchronized user and role data across Fusion Applications and FDI ensures that users aren’t created separately in FDI during provisioning. When SSO is set up, authentication and authorization are driven by a single identity source, and the mappings for who a user is and what they can do (their job roles) come from Fusion Applications. By synchronizing these identities and role assignments before provisioning the FDI instance, FDI can rely on the existing user records and their permissions rather than creating new ones locally. This keeps access control consistent, reduces administrative overhead, and avoids the confusion and maintenance burden of duplicate accounts and divergent role mappings. Manual imports would recreate separate user records in FDI and require ongoing synchronization, increasing drift and administrative effort. Disabling SSO would break the centralized identity model, leading to multiple credentials and possible inconsistencies. Using a separate identity service can complicate the lifecycle of users and often still requires reconciliation with Fusion Applications’ roles.

Centralized identity management through Single Sign-On and synchronized user and role data across Fusion Applications and FDI ensures that users aren’t created separately in FDI during provisioning. When SSO is set up, authentication and authorization are driven by a single identity source, and the mappings for who a user is and what they can do (their job roles) come from Fusion Applications. By synchronizing these identities and role assignments before provisioning the FDI instance, FDI can rely on the existing user records and their permissions rather than creating new ones locally. This keeps access control consistent, reduces administrative overhead, and avoids the confusion and maintenance burden of duplicate accounts and divergent role mappings.

Manual imports would recreate separate user records in FDI and require ongoing synchronization, increasing drift and administrative effort. Disabling SSO would break the centralized identity model, leading to multiple credentials and possible inconsistencies. Using a separate identity service can complicate the lifecycle of users and often still requires reconciliation with Fusion Applications’ roles.