To use the FlexDeploy OCI Plugin, follow these steps to get the information FlexDeploy requires to connect.

• Create User in IAM/IDCS

• Prepare and configure PEM Key

  • Generate API Signing Key

Create User in IAM/IDCS

Create a user in IAM/IDCS for FlexDeploy to connect with and put that user in at least one group with any desired permissions. You can skip this if the user exists already. We will create the API Key for this user.

Prepare and configure PEM Key

Generate API Signing Key

Navigate to Oracle if you are using your own account. Otherwise, browse to the correct user and click Api Keys on the left side.

Click Add API Key.

Click Download private Key.

Open

Click Add.

Your fingerprint, user, and tenancy will be shown on the confirmation screen. You will need all of them, so don’t lose, them. Copy them to notepad or something to keep them safe before you start filling them into FlexDeploy.

These lines are all entered into FlexDeploy.

If you made a system user that doesn’t need to login without an API Key, turn off the other authentication methods:

Open

Configuring the Cloud Account

OCI plugin operations require the FDOCI_CLOUD_ACCOUNT_CODEtarget property. The cloud account can be managed directly through the target property drop-down (available since version FlexDeploy 9.0.0.4) or on the Integrations > Cloud page. Below is a description of the OIC cloud account properties. To validate your configurations, use the Test Connection option.

Prior to FlexDeploy 9.0.0.5, OAuthJWTAssertion required using a Java KeyStore for the Private Key and Certificate. When upgrading from FlexDeploy 9.0.0.4 or earlier, the OIC cloud account will automatically migrate to use Private Key and Certificate credentials from the configured KeyStore, eliminating the need to maintain the KeyStore on the file system. As a result, the KeyStore Path, KeyStore Password, Private Key Alias, Private Key Password, and Certificate Algorithm properties are now replaced with the Private Key and Certificate properties.