Using API to retrieve credentials

Implemented

Using API to retrieve credentials

0 vote

avatar
rdiaky
Disabled

Hello,

I'm posting this feature request on behalf of a customer.
The Customer uses API to retrieve credentials, and they usually get errors even though they are retrieved correctly.
DVLS version: 2024.1.12
The root cause is multiple programmatic access attempts from their automation system.
Also, this has raised the issue of being unable to track which of the application's automation tasks has requested access.
Due to how the application works, all tasks will share the same API application, so they know it came from SnapLogic but not which task.

Other products that they use have implemented solutions for similar issues.

They propose to allow an optional field (varchar(255)) as part of the login request that would also be part of the primary key. If needed, they can then send an external ID for every attempt to log in. This would both prevent the key-duplication error and give them a way of identifying which task from the application requested a login.

So the POST body would be one of these 3:

{
"appKey": "myKeyGuid",
"appSecret": "mySecret"

}

{
"appKey": "myKeyGuid",
"appSecret": "mySecret",
"externalId": null
}

{
"appKey": "myKeyGuid",
"appSecret": "mySecret",
"externalId": "myProcessRuntimeID"
}


Thanks

All Comments (1)

avatar

Hello,

We have created a ticket in our backlog and assigned it. We will post back here once we have an update.

Best regards,

François Dubois