
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hy Team,
use case-" Auto approval of emergency access in PAM using IDM workflow (REST API)"
I created a workflow for auto approval of emergency access using REST API and the workflow is working properly. when the user requested through request form, the REST API calls and the emergency access is auto approved. But when the requester login into PAM user console and launch the emergency access session ,it shows error "user name and password is incorrect".i also try in the PAM REST API but i am facing same issue.
REST API code:
"Request": {
"id": "af81b410-f92e-11ea-ad4e-55e325d9a838",
"type": "EmergencyRequest",
"action": "approve",
"comment": "You are granted access to the ldap server.",
"runas": "shivam",
"runhost": "192.168.20.4",
"target": "RDP",
"requestperiod": 360,
"credential": "a838d1ca-ede4-11ea-ab29-c18521c8a0e7"
}
}
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
Thank you for your response.The issue was resolved. If we put domain\username as runas in rest api it will simply take runas as domainusername but if we put domain\\username then it will consider the runas as domain\username and successfully approve the emergency request with resource and credential.
{
"Request": {
"id": "af81b410-f92e-11ea-ad4e-55e325d9a838",
"type": "EmergencyRequest",
"action": "approve",
"comment": "You are granted access to the ldap server.",
"runas": "idm\\shivam",
"runhost": "192.168.20.4",
"target": "RDP",
"requestperiod": 360,
"credential": "a838d1ca-ede4-11ea-ab29-c18521c8a0e7"
}
}

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
If so, this is Windows presenting this error that the Login credentials are incorrect:
"The user name or password is incorrect. Try again."
So whichever Credential is being assigned when approving the Emergency Access Request must be incorrect. Perhaps it is that the user name or password is incorrectly stored or entered into the Vault Resource in PAM or perhaps the credential id used in the REST auto-approval is referencing an incorrect credential. Perhaps you could try approving manually with the PAM User Console and selecting the Credential there to help rule out any issue with the REST API automation first.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
Thank you for your response.The issue was resolved. If we put domain\username as runas in rest api it will simply take runas as domainusername but if we put domain\\username then it will consider the runas as domain\username and successfully approve the emergency request with resource and credential.
{
"Request": {
"id": "af81b410-f92e-11ea-ad4e-55e325d9a838",
"type": "EmergencyRequest",
"action": "approve",
"comment": "You are granted access to the ldap server.",
"runas": "idm\\shivam",
"runhost": "192.168.20.4",
"target": "RDP",
"requestperiod": 360,
"credential": "a838d1ca-ede4-11ea-ab29-c18521c8a0e7"
}
}