text
stringlengths 65
20k
|
|---|
Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate . |
In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed. |
The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password. |
To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close . |
The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once. |
2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential. |
The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential. |
4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials . |
The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen. |
The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values. |
This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above. |
Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ. |
Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs. |
For more information, refer to the table in Gather Needed Information .6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials. |
6.Click Generate .The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws. |
The generated credential is displayed.The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials. |
The client credential includes the client credential's OCID and a one-time password.7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential. |
7.Note the password, then click Close .The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password). |
The credential password appears here just once.There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials. |
There is no way to retrieve a password; if you lose it, you must regenerate the credential.8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential. |
8.If needed, edit the client credential.The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated. |
The generated client credential is listed under OAuth 2.0 Client Credentials .You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command. |
You can view or change its attributes and regenerate the client secret if needed on the credential details screen.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above. |
Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-10 Obtain an OAuth Bearer Token Once you have the OAuth client credential configured, you can get an OAuth bearer token based on the generated values.To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database. |
To obtain an OAuth bearer token, enter the following values in your API request, using either POSTMAN or curl: 1.Client ID and secret: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.UPI stripe token request endpoint (POST): https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token 3.Scope definition in the POST request payload: For this instance the scope definition is a concatenation of the audience and scope (exactly) as defined in the client credentials creation step above.'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role. |
'grant_type=client_credentials' 'scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 4.Request: curl -X POST \ https://idcs-364c06d3202948828edee2b8ba4dbc16.idcs.identity.us- phoenix-1.oci.oraclecloud.com/oauth2/v1/token \ -H 'Accept: application/json'\ -H 'Authorization: BasicChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-11 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2amx tNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRg=='\ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -H 'cache-control: no-cache' \ -d 'grant_type=client_credentials&scope=https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443urn:opc:resource:consumer::all https:// 1403FE2A654445B7AAC83480F67E8C48.0001.integration.dev.ocp.oc- test.com:443/ic/api' 5.Response: { "access_token": "eyJ4NXQjUzI1NiI6Ijc3NmdPRkNZZUxSZ0J2Q2JFcHE4dkg3OVc1UUxhWG91Q1c1QkN0U0xEek EiLCJ4NXQiOiJtejFrdVE4TEJudUF1VEs3S3EwQ3lRUlpCMmsiLCJraWQiOiJhc3ctb2F1dGhfb 2MxXzY1MmI4YjI5IiwiYWxnIjoiUlMyNTYifQ.eyJ1c2VyX3R6IjoiTVNUIiwic3ViIjoiam9ob i5kb2VAdGVzdC5jb20iLCJ1c2VyX2xvY2FsZSI6IkVOIiwidXNlcl9kaXNwbGF5bmFtZSI6Impv aG4uZG9lQHRlc3QuY29tIiwic3ViX21hcHBpbmdhdHRyIjoidXNlck5hbWUiLCJpc3MiOiJhdXR oU2VydmljZS5vcmFjbGUuY29tIiwidG9rX3R5cGUiOiJBVCIsInB0eXBlIjoidXNlciIsInVzZX JfdGVuYW50bmFtZSI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYiLCJjb GllbnRfaWQiOiJvY2lkMS5jcmVkZW50aWFsLm9jMS4uYWFhYWFhYWF1bHBscGgzM21hcWx0Y3R0 cHBqb3liNTZqbG01YXN4NWlrY29qbnR2emo1bW52cDI1cW5xIiwiYXVkIjpbImh0dHBzOlwvXC9 0ZXN0ZG5zdXBpNnVzaW5nbWlnbGFiLWlkYWF0MzFkanZpcy1jcGkuMDAwMS5pbnRlZ3JhdGlvbi 5kZXYub2NwLm9jLXRlc3QuY29tOjQ0MyIsImh0dHBzOlwvXC8xNDAzRkUyQTY1NDQ0NUI3QUFDO DM0ODBGNjdFOEM0OC4wMDAxLmludGVncmF0aW9uLmRldi5vY3Aub2MtdGVzdC5jb206NDQzIiwi dXJuOm9wYzpsYmFhczpsb2dpY2FsZ3VpZD0xNDAzRkUyQTY1NDQ0NUI3QUFDODM0ODBGNjdFOEM 0OCJdLCJ1c2VyX2lkIjoib2NpZDEudXNlci5vYzEuLmFhYWFhYWFhMjdqZW1vcmZ3YXp2ZDVtc2 JiNzJxM2hlN3Frd2JzeXlkNzd0bWxvbmVoYzU0aGs1cG9jcSIsInN1Yl90eXBlIjoidXNlciIsI nNjb3BlIjoidXJuOm9wYzpyZXNvdXJjZTpjb25zdW1lcjo6YWxsIFwvaWNcL2FwaSIsImNsaWVu dF90ZW5hbnRuYW1lIjoiaWRjcy0zNjRjMDZkMzIwMjk0ODgyOGVkZWUyYjhiYTRkYmMxNiIsInV zZXJfbGFuZyI6IkVOIiwiZXhwIjoxNTk2NTYzNzcwLCJpYXQiOjE1OTY1NjAxNzAsImNsaWVudF 9ndWlkIjoib2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwa m95YjU2amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucSIsImNsaWVudF9uYW1lIjoibXktdGVz dC1pbnN0YW5jZS1jbGllbnQiLCJ0ZW5hbnRfaXNzIjoiaHR0cHM6XC9cL2lkY3MtYmEyZDI0NDg 0MmJhNGZiYWJlNmIzM2VlMGIxM2MwYzEuaWRjcy5pZGVudGl0eS51cy1hc2hidXJuLTEub2NpLm 9yYWNsZWNsb3VkLmNvbSIsImp0aSI6IjkyZGNkMDQzLTc0MDYtNGJhZi1hZTMxLTVmY2JmZTk4Y zRiNSIsInRlbmFudCI6ImlkY3MtMzY0YzA2ZDMyMDI5NDg4MjhlZGVlMmI4YmE0ZGJjMTYifQ.J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails. |
J 8atPO-RjSsplzzzTYkT5_NCYo33gfHQJgZomJ3dZvrSpGdPDJ6Xxtb-UrLMLFGOZEaw-b4- JaY_z4KWETjlicseeMTBIgnpeiqf0QppqS0vJeMzy3kA_EIJrtcX_NQglOUYpGtyNq5- HTix6fPULYMf_ZMhLm7XAh551QAwL_TP_gz1QAXRsbYkzN_19Hs_kgJZ- KlZ2cwYLl2H3o36x2d2V3ESZNejPwSwutky8nT0bLBT78kwfc3YRzkhThb613XD3r4oLyYLGbTi e9wHbufHjkAbcZRX7JR_hPjSxhm_ijVlOlEvFCy5Smn5-vss3dDBKJocGIIpbSfFyffxHQ", "token_type": "Bearer", "expires_in": "3600" } Use the Bearer Token to Invoke Oracle Integration APIs Using the bearer token obtained in Obtain an OAuth Bearer Token , you can now invoke Oracle Integration APIs.See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent. |
See REST API for Oracle Integration .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-12For example: curl -X GET \ https://testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/integrations \ -H 'Authorization: Bearer eyJ4NXQjUz........'\ -H 'cache-control: no-cache' Configure Basic Authentication Using Client Credentials To configure Basic Authentication for invoking Oracle Integration APIs in an Oracle Cloud Infrastructure US Government Cloud environment, use the client ID and secret from an OAuth 2.0 client credential as the Basic Authentication credentials.As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration. |
As a general Oracle Cloud Infrastructure security rule, Basic Authentication is not recommended as an authentication method, due to its inherent flaws.Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment. |
Oracle Cloud Infrastructure's IAM model doesn't allow user login credentials to be used as Basic Authentication credentials.This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials. |
This means that login credentials (to log into the Oracle Cloud Infrastructure Console or to the Oracle Integration functional console) can't be used when invoking Oracle Integration APIs as a Basic Authentication credential.Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication. |
Instead, use the ID and secret from OAuth 2.0 client credentials as the Basic Authentication credentials (user name and password).To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials. |
To configure OAuth client credentials as Basic Authentication credentials: 1.Create OAuth client credentials.Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials . |
Follow the steps in Configure OAuth 2.0 Authentication Using Client Credentials on generating the client credential.Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration. |
Note the client ID and client secret that are generated.Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials . |
Example values: Client ID: ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvzj5m nvp25qnq Client Secret: i7BKNOG:1z1A)bqaY(]F 2.Use the OAuth credentials as the Basic Auth credentials directly in a command.See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console. |
See these examples that use values from above.Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3). |
Using base64 encoding: # echo 'ocid1.credential.oc1..aaaaaaaaulplph33maqltcttppjoyb56jlm5asx5ikcojntvz j5mnvp25qnq:i7BKNOG:1z1A)bqaY(]F' | base64 b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo= Returned base64 string in the Authorization header: curl -X GET \ testdnsupi6usingmiglab-idaat31djvis-cpi.0001.integration.dev.ocp.oc- test.com:443/ic/api/integration/v1/connections \ -H 'Authorization: Basic Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-13b2NpZDEuY3JlZGVudGlhbC5vYzEuLmFhYWFhYWFhdWxwbHBoMzNtYXFsdGN0dHBwam95YjU2 amxtNWFzeDVpa2Nvam50dnpqNW1udnAyNXFucTppN0JLTk9HOjF6MUEpYnFhWShdRgo=' \ -H 'cache-control: no-cache' Configure the Connectivity Agent The Connectivity Agent is required to connect Oracle Integration with an on-premises database.To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2). |
To use the Connectivity Agent in an Oracle Cloud Infrastructure US Government Cloud environment, it needs a non-federated account with the ServiceAdministrator role.If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains. |
If you try to run the Connectivity Agent installation as a federated user, it fails.To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud . |
To prevent this issue, follow the steps below to configure a nonfederated (IAM) user to install the agent.This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region. |
This user enables the agent to communicate with Oracle Integration.1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created. |
1.Configure a user with permissions to install the agent, by adding an IAM policy that assigns the ServiceAdministrator role for the compartment.Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services . |
Syntax: allow group OICAdminGroup to be ServiceAdministrator for integration- instances in compartment OICCompartment Example: allow group OICServiceDevelopers to be ServiceAdministrator for integration-instances in compartment OrganizationCompartment 2.In the Connectivity Agent, configure Basic Authentication using client credentials.Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration . |
Use the client ID and secret instead of a username and password for the authentication.a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance. |
a.Generate the OAuth client credentials.See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use. |
See Generate the Client Credentials .b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments. |
b.Use the client credentials in Basic Authentication in the Connectivity Agent configuration.See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created. |
See Configure Basic Authentication Using Client Credentials .3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance. |
3.If you need to restart the Connectivity Agent at some point, ensure that the username and password credentials for the user you configured above are still valid.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-143 Work with Oracle Integration Generation 2 Instances on Oracle Cloud Infrastructure US Government Cloud Create and edit Oracle Integration Generation 2 instances in the Oracle Cloud Infrastructure Console.Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment. |
Topics: Create an Oracle Integration Instance View Instance Details Create an Oracle Integration Instance Note: You cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Defense Cloud (realm key: OC3).Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create . |
Additionally, most organizations cannot provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud (realm key: OC2).The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance. |
The only organization that can provision a new Oracle Integration Generation 2 instance in the Oracle US Government Cloud are tenancies that do not use identity domains.To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy. |
To create an Oracle Integration 3 instance, see Create an Oracle Integration Instance in Using Oracle Integration 3 on Oracle Cloud Infrastructure US Government Cloud .To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one. |
To create an Oracle Integration instance in a selected compartment: 1.In the upper corner, note your selected region.Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm. |
Once created, instances are visible only in the region in which they were created.2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud. |
2.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour. |
Under Application Integration , click Integration .3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration. |
3-1 3.From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance.You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour. |
You may need to expand the + icon to find the compartment to use.Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL). |
Compartments can contain other compartments.It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating. |
It may take several minutes for the new compartment to appear after the policy has been created.Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs. |
Note: Do NOT select the root or ManagedCompartmentForPaaS compartment in which to create your instance.The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected. |
The page is refreshed to show any existing instances in that compartment.4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud. |
4.Click Create .5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud. |
5.Enter the following details and click Create : Field Description Display Name Enter the display name for the instance.Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model . |
Note that the display name becomes part of the URL for accessing the instance.Chapter 3 Create an Oracle Integration Instance 3-2Field Description Consumption Model Lists consumption models available in this tenancy.Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance. |
Typically, one model is displayed, but multiple consumption models are listed if your tenancy is enabled for more than one.Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time. |
Available models include: Metered (Universal Credit) Oracle Integration Government Note: Oracle Integration Government is a license and doesnt specify the realm.License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed. |
License Type Select to create a new Oracle Integration license in the cloud.This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes. |
This provides you with packages of 5K messages per hour.Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column. |
Select to bring an existing Oracle Fusion Middleware license to the cloud for use with Oracle Integration.This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances. |
This provides you with packages of 20K messages per hour.This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services . |
This option is also known as bring your own license (BYOL).Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration . |
Message Packs The message pack options available for selection are based on the version of Oracle Integration instance you are creating.Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name. |
Select the number of message packs.The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed. |
The total number of messages available per pack is based on the License Type option you selected.You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running. |
You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources . |
You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware). |
Typically, the selected model is displayed after Consumption Model .If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed. |
If multiple consumption models are listed, choose the model you'd like used for this instance.Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page. |
Instance creation takes some time.If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center . |
If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed.Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration. |
Wait a few more minutes.6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console. |
6.When instance creation completes successfully, the instance shows as Active in the State column.View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings. |
View Instance Details You can view details about a provisioned instance and perform tasks such as accessing the instance login page to design integrations, viewing custom endpoint details, editing an instance, adding tags, and deleting instances.1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment. |
1.Open the navigation menu and click Developer Services .Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete. |
Under Application Integration , click Integration .2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 . |
2.In the Display Name column, click a specific instance name.The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance. |
The Details page is displayed.The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy. |
The word Active is displayed beneath the green circle to indicate that this instance is running.Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation. |
Chapter 3 View Instance Details 3-3 The following table describes the key information shown on the instance details page: Field Description Integration Instance Information tab Creation date Last updated date (for example, the last time started) Selected consumption (billable) model Edition (standard or enterprise) OCID value that uniquely identifies the instance, which can be shown in full and easily copied Network access setting, which you can change by clicking Network Access under Resources .Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance. |
Service Console URL, which can be shown in full and easily copied License type (either a new cloud license or an existing license brought over from Oracle Fusion Middleware).If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics. |
If you are viewing an Oracle Integration for SaaS instance, the License Type field is not displayed.Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics.See Viewing Message Metrics in Provisioning and Administering Oracle Integration Generation 2. |
Number of message packs and the quantity of messages in each pack Service Console Click to access the login page.See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics.See Viewing Message Metrics in Provisioning and Administering Oracle Integration Generation 2.Work Requests Lists instance life cycle activity, such as instance creation time, instance stop and start times, and so on. |
See the Oracle Integration Help Center .Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics.See Viewing Message Metrics in Provisioning and Administering Oracle Integration Generation 2.Work Requests Lists instance life cycle activity, such as instance creation time, instance stop and start times, and so on.Network Access Click Edit to change the Network Access setting. |
Note: You can also access the login page from the main Oracle Cloud Infrastructure Console page for Oracle Integration.At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics.See Viewing Message Metrics in Provisioning and Administering Oracle Integration Generation 2.Work Requests Lists instance life cycle activity, such as instance creation time, instance stop and start times, and so on.Network Access Click Edit to change the Network Access setting.Select Restrict Network Access to disallow inbound traffic from external networks.Chapter 3 View Instance Details 3-5Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2 F58803-05 February 2023 Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2, F58803-05 Copyright 2022, 2023, Oracle and/or its affiliates. |
At the far right, click for the specific instance, and select Service Console.Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics.See Viewing Message Metrics in Provisioning and Administering Oracle Integration Generation 2.Work Requests Lists instance life cycle activity, such as instance creation time, instance stop and start times, and so on.Network Access Click Edit to change the Network Access setting.Select Restrict Network Access to disallow inbound traffic from external networks.Chapter 3 View Instance Details 3-5Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2 F58803-05 February 2023 Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2, F58803-05 Copyright 2022, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. |
Edit Click to edit your settings.See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics.See Viewing Message Metrics in Provisioning and Administering Oracle Integration Generation 2.Work Requests Lists instance life cycle activity, such as instance creation time, instance stop and start times, and so on.Network Access Click Edit to change the Network Access setting.Select Restrict Network Access to disallow inbound traffic from external networks.Chapter 3 View Instance Details 3-5Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2 F58803-05 February 2023 Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2, F58803-05 Copyright 2022, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. |
See Editing the Edition, License Type, Message Packs, and Custom Endpoint of an Instance in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 View Instance Details 3-4Field Description Move Click to move the instance to a different compartment.This action can take some time to complete.See Moving an Instance to a Different Compartment in Provisioning and Administering Oracle Integration Generation 2 .Add Tags Click to add tags to the instance.You can use tags to search for and categorize your instances in your tenancy.See Resource Tags in the Oracle Cloud Infrastructure Documentation.More Actions Contains options to stop, start, or delete the instance.See in Provisioning and Administering Oracle Integration Generation 2 : Stopping and Starting an Oracle Integration Instance Deleting an Instance Metrics Displays message metrics.See Viewing Message Metrics in Provisioning and Administering Oracle Integration Generation 2.Work Requests Lists instance life cycle activity, such as instance creation time, instance stop and start times, and so on.Network Access Click Edit to change the Network Access setting.Select Restrict Network Access to disallow inbound traffic from external networks.Chapter 3 View Instance Details 3-5Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2 F58803-05 February 2023 Oracle Cloud Using the SAP ASE (Sybase) Adapter with Oracle Integration Generation 2, F58803-05 Copyright 2022, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.