When using password-based authentication to connect FDI to a test Fusion Cloud Application, what must you do to run the pipeline?

When using password-based authentication to connect FDI to a test Fusion Cloud Application, what must you do to run the pipeline?

• A. Update the applicable user's credentials if passwords aren't the same
• B. Reset all passwords
• C. Switch to OAuth
• D. Disable password-based authentication

Answer: (A)

The key idea is that password-based authentication requires the credentials used by the integration (FDI) to match the current Fusion Cloud user password. If the Fusion Cloud password for the user used by the pipeline changes or differs from what FDI has stored, the authentication will fail, so you must update the applicable user’s credentials in FDI to the new password. This keeps the connection valid and allows the pipeline to run. The other options aren’t necessary here: resetting all passwords is overkill and not required for a single integration, switching to OAuth changes the authentication method rather than addressing a mismatch in passwords, and disabling password-based authentication would prevent password auth from working rather than enabling the pipeline.

The key idea is that password-based authentication requires the credentials used by the integration (FDI) to match the current Fusion Cloud user password. If the Fusion Cloud password for the user used by the pipeline changes or differs from what FDI has stored, the authentication will fail, so you must update the applicable user’s credentials in FDI to the new password. This keeps the connection valid and allows the pipeline to run.

The other options aren’t necessary here: resetting all passwords is overkill and not required for a single integration, switching to OAuth changes the authentication method rather than addressing a mismatch in passwords, and disabling password-based authentication would prevent password auth from working rather than enabling the pipeline.