Content Connector Execution Flow

From the Oracle Content Management UI Assets page, the user can click Add and choose a content connector from the menu.

Based on the authorization type defined, the OAuth flow is triggered or the user is prompted to add a user name and password for the Basic Auth flow (if a central account has not been configured in the administration UI). For No Auth, the content connector picker is launched directly without invoking any authorization screen.

After successful authorization, the configured file picker (either common or custom) is launched. It lists the files available to the user from the remote store.

The user can select one or more files. The selected files list is passed to the connector framework. The connector framework then makes REST API calls to the remote content connector to fetch the content of the assets being added and copies them into the asset repository. This happens as a background process; however, the status of the add is displayed in the UI where success and failure can be tracked for each asset added. Refer to the diagnostic logs for any failures.