When the Visual Builder, Integration, or Oracle Cloud Applications instance in your environment is not in the same identity domain as your VB Studio instance, you can use OAuth tokens to securely access the instance.

1. OAuth tokens for your instance can be set up while adding the instance to your environment, or when setting up builds.
   Follow the steps to set up your OAuth configuration for Visual Builder instances:

   • To create an environment with a Visual Builder instance, see Create and Set Up a Project for Development.
   • To configure the deployment build job used by the Publish action in the Designer, see Configure the Deployment Job. OAuth is also supported in other build jobs used to import and export data, lock, unlock, roll back, or undeploy a visual application.

   Follow the steps to set up your OAuth configuration for Oracle Cloud Application instances:

   • To create an environment with an Oracle Cloud Applications instance, see Add an Oracle Cloud Applications instance to your environment.
   • To configure the deployment build job used by the Publish action in the Designer, see Create a Deployment Build Job. OAuth is also supported in build jobs used to delete an extension.

   Follow the steps to set up your OAuth configuration for Oracle Integration instances:

   • To create an environment with an Oracle Integration instance, see Add an Oracle Integration Instance to an Environment.
   • To configure build jobs used to import and export Integration artifacts from and to an Oracle Integration instance (as well as to activate or delete an Integration), see Manage Integrations. OAuth is also supported in build jobs used to manage Integration projects, packages, lookups, and connections.

   Before any OAuth tokens can be created, authorization must be provided to handle OAuth requests for your environment's instance. VB Studio can automatically detect the instance being added from a different identity domain and will prompt you for authorization. Click Authorize, when prompted, then sign in with credentials that can connect and deploy to the target instance.

   Note:

   It is recommended that you authorize your OAuth connection during initial configuration. If you skip this step, developers won't be able to publish changes from the Designer until the required authorization is provided.
2. OAuth tokens (access and refresh) are typically cycled during regular use. If a token expires during extended periods of inactivity (say, when you're away on vacation), you'll need to renew the token:
   • To renew OAuth tokens on the Environments page, click Actions and select Renew OAuth Access.
   • To renew OAuth tokens on the Builds page, locate your build job, then click Renew Authorization on the Steps tab. You can also run the job manually, so you'll be prompted to authorize any expired OAuth tokens.