Which approach best aligns FAW security with Fusion Applications without duplicating access provisioning?

Which approach best aligns FAW security with Fusion Applications without duplicating access provisioning?

• A. Replicating the entire security model in FAW.
• B. SSO between FAW and Fusion Applications with synchronized roles.
• C. Creating separate, independent FAW credentials.
• D. Disabling security in FAW and relying on Fusion Applications.

Answer: (B)

Single Sign-On with synchronized roles across FAW and Fusion Applications lets users authenticate once and receive the same entitlements in both systems. By centralizing authentication and keeping role definitions in a single place, you avoid creating separate provisioning for each application. When a user gains or loses a role, the change is reflected consistently in both FAW and Fusion Applications, so access stays in sync without duplicating work. This approach reduces administrative overhead, minimizes policy drift, and provides a smoother user experience since users don’t have to manage multiple credentials or undergo repeated provisioning. Duplicating the entire security model in FAW would create two parallel security environments that must be kept in sync, increasing maintenance and the risk of inconsistent access control. Using independent FAW credentials means you’d have to provision and manage users separately for each system, again driving duplication and inefficiency. Disabling security in FAW and relying on Fusion Applications is unsafe and undermines overall protection, leaving critical boundaries unenforced.

Single Sign-On with synchronized roles across FAW and Fusion Applications lets users authenticate once and receive the same entitlements in both systems. By centralizing authentication and keeping role definitions in a single place, you avoid creating separate provisioning for each application. When a user gains or loses a role, the change is reflected consistently in both FAW and Fusion Applications, so access stays in sync without duplicating work. This approach reduces administrative overhead, minimizes policy drift, and provides a smoother user experience since users don’t have to manage multiple credentials or undergo repeated provisioning.

Duplicating the entire security model in FAW would create two parallel security environments that must be kept in sync, increasing maintenance and the risk of inconsistent access control. Using independent FAW credentials means you’d have to provision and manage users separately for each system, again driving duplication and inefficiency. Disabling security in FAW and relying on Fusion Applications is unsafe and undermines overall protection, leaving critical boundaries unenforced.