1. Extending Oracle Cloud Applications with Visual Builder Studio
  2. Build an Extension
  3. Work With Services
  4. Configure Authentication Types for Service Connections and Backends

Configure Authentication Types for Service Connections and Backends

When you create a service connection or backend with a new server or edit an existing server in a service connection, you configure the authentication that your extension uses with external services.

Note:

Note:

For service connections created after the 23.10 release, server authentication types must be updated from the backend associated with the service connection.

The dialogs that enable you to add a new server to or edit an existing server in a service connection enable you set or override the server's authentication settings.

Note:

An administrator may need to configure the VB Studio environment settings for backend services or the settings of the external service or identity provider before you can connect to the service.

The REST APIs that you are connecting to must have CORS support for both the VB and Oracle Cloud Applications domains. Without this setting for the REST APIs, you'll see a CORS Preflight error when the REST API is called. The backends that are inherited from the Unified Application must be pre-configured for CORS to allow access to the VB domain.

To connect to a service that requires authentication, you need to select the appropriate authentication option from the Authentication drop-down list.

  • The default setting of None is sufficient to connect to a service that is available on HTTPS, doesn't require authentication, and has no special CORS requirement.

    In this case, any authenticated end user of the extension will be able to access the service. Sending a request to a service that requires authentication will return an error if you don't provide the authentication details. No authentication headers are sent but you do have the option of passing a custom authorization header to the service if one is required.

  • Oracle Cloud Account – Select this mechanism to communicate with Oracle Cloud Applications services.

    The user must sign in with the credentials of a valid account in the Oracle Identity Cloud Service (IDCS) that is associated with Visual Builder. The user's identity is converted into a user assertion that is then converted into an IDCS-issued JWT token for a scope that is equivalent to the base URL of the service being called.

    For example, if the service's URL is https://fa.oraclecloud.com/myservice, the token will be created for the scope of https://fa.oraclecloud.com.