Table of Contents

Search

  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using App Connections
  9. System Services, Listeners and Connectors
  10. Designing Human Tasks

Design

Design

Updating sensitive field values for app connections

Updating sensitive field values for app connections

You can use the update resource to update the sensitive field values for app connections. You can update fields for a single app connection or multiple app connections.
To update the app connections using the update resource, you must be assigned the Admin, Deployer, Designer, or Operator role.
When you export an asset, sensitive fields such as passwords, access keys, and secret keys are not exported. After you import an app connection, you can add the connection and the fields that you want to update as input data in a REST client such as Postman. The input data consists of the Global Identifier/Global Unique Identifier (GUID) of the connection and a key-value pair of attributes to be updated. In addition, you can provide attributes for the consumers and producers of the connection. Consumers refer to the event sources and producers refer to the event targets. For more information about GUID, see the lookup resource and finding assets resource in
REST API Reference
in the Data Integration help.
To update the field values, use the following URL:
<Informatica Intelligent Cloud Services URL>/active-bpel/asset/v1/update?assetType=AppConnection
You can add the input data as shown in the following sample:
PUT <baseApiUrl>/active-bpel/asset/v1/update?assetType=AppConnection Content-Type: application/json Accept: application/json INFA-SESSION-ID: <Infa-Session-ID> { "connections": [ { "guid": { "$t": "<guidvalue>" }, "attributes": [ { "key": { "$t": "Access Key" }, "value": { "$t": "<AccessKeyvalue>" } }, { "key": { "$t": "Secret Key" }, "value": { "$t": "<SecretKeyvalue>" } } ], "consumers": [ { "name": { "$t": "consumer1" }, "attributes": [ { "key": { "$t": "attribute1" }, "value": { "$t": "<AttributeValue>" } } ] } ], "producers": [ { "name": { "$t": "producer1" }, "attributes": [ { "key": { "$t": "attribute1" }, "value": { "$t": "<AttributeValue>" } } ] } ] }, { "guid": { "$t": "<guidvalue>" }, "attributes": [ { "key": { "$t": "Password" }, "value": { "$t": "<Passwordvalue>" } } ] } ] }
You can use the login resource to get the
INFA-SESSION-ID
. For more information about the login resource, see
REST API Reference
in the Data Integration help.
If the fields are successfully updated, you receive the following response:
{ "status": { "$t": "SUCCESS" } }
The fields are updated based on the GUID of the connection. If the GUID is not found, you receive the following response:
{ "status": { "$t": "FAILED" }, "errorDetails": { "error": { "$t": "Update failed for assets" }, "failedAssets": { "updateAssetFaultInfo": { "xmlns": "https://com.informatica.icrt/2021/08/updateAssets.xsd", "xmlns$aetgt": "https://com.informatica.icrt/2021/08/updateAssets.xsd", "name": {}, "GUID": { "$t": "<Incorrect guid value>" }, "fault": { "$t": "Entry not found for GUID." } } } } }

0 COMMENTS

We’d like to hear from you!