<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A1CiYyCQKOkta Classic EngineAPI Access ManagementAnswered2024-07-26T18:52:23.000Z2024-02-21T13:04:24.000Z2024-02-22T01:02:16.000Z

DekeyserC.91209 (Customer) asked a question.

Adobe Experience platform - Roles management with API and workflows

Currently trying to implement AEP (Adobe experience platform) roles management via workflows with API calls.

Is there any built-in connector in okta in order to manage this ? (since Adobe user management connector don't offer to manage roles, nor the custom API calls, since it's not the correct endpoint).

Is there any standard way to handle those API calls, or any way to avoid renewing Oauth token manually in the workflows?


  • TimL.58332 (Workflows)

    @DekeyserC.91209 (Customer)​ -- A link to the API documentation you are referencing would be helpful.

     

    Essentially you will need to leverage the API Connector or build your own custom connector with Connector Builder. (Note: API Connector is going to be the far less involved method). You will need to either leverage the built-in auth options in the API Connector (assuming it meets the criteria for what the endpoint requires) or you will need to build out the auth process manually to obtain the "access token" required for the endpoints.

     

    Once you have the credentials to perform actions then it will just be raw calling the endpoints with the METHOD / Header / Body required per the vendors documentation.

     

    So assuming the documentation link is: https://experienceleague.adobe.com/docs/experience-platform/landing/platform-apis/api-guide.html?lang=en

     

    from the cURL example they provide:

     

    curl -X GET \

    https://platform.adobe.io/data/foundation/schemaregistry/global/classes \

    -H 'Accept: application/vnd.adobe.xed-id+json' \

    -H 'Authorization: Bearer {ACCESS_TOKEN}' \

    -H 'x-api-key: {API_KEY}' \

    -H 'x-gw-ims-org-id: {ORG_ID}' \

    -H 'x-sandbox-name: {SANDBOX_NAME}'

     

     

    They require you to pass in a bunch of required headers. Based on this you would not be able to leverage the API Connectors built-in auth methods (However, Connector builder could be leveraged). Instead you would need to use "No Auth" and pass in a JSON header object with the required headers (and the valid values).

     

    The vendor's documentation should show the steps to acquire those specific values (which may be additional API calls).

    Expand Post
This question is closed.
Loading
Adobe Experience platform - Roles management with API and workflows