Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Azure provisioning REST Connection ( Not the Azure AD) - Add Access Through ARS Request

saqib
New Contributor
New Contributor

I have created a Privilage in Resource Group Entitlement type , Which allows only Enum / String , I enabled Enum with Reader , Contributor , Owner .

saqib_0-1726089302368.png

 

When i request For Resource Group with Reader as Privilage type through ARS and submit request. Provisioning tasks are getting failed. 

 

I'm not able to view the json  it generated in logs. Response received is null with status code null.

Logs attached, Please let me know if any one implemented the provisioning of resource group.

 

OOTB JSON is : 

{ "name": "ResourceGroup",
"connection": "userAuth",
"privilegeEntitlement":{"privEntType":"RoleDefinition","privAttrName":"Roles"},
"url": "https://management.azure.com${entitlementValue.customproperty4}/providers/Microsoft.Authorization/roleAssignments/${UUID.randomUUID().toString()}?api-version=2015-07-01",
"httpMethod": "PUT",
"httpParams": "{ \"properties\": { \"roleDefinitionId\": \"${privEntVal.customproperty4}\", \"principalId\": \"${account.accountID}\" } }",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json"
}

 

10 REPLIES 10

rushikeshvartak
All-Star
All-Star
  • Any reason for not using OOTB Azure AD connection ?
  • Please share logs in text format 
  • Please confirm if its working from postman?

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

For provisioning of Azure ( Not Azure AD ), Rest is recommended as per docs. and yes it is working form post man.

stalluri
Valued Contributor
Valued Contributor

@saqib 

OOTB Azure is working fine, May I know why you want to use Rest connector?


Best Regards,
Sam Talluri
If you find this a helpful response, kindly consider selecting Accept As Solution and clicking on the kudos button.

saqib
New Contributor
New Contributor

OOTB Azure can be used for provisioning , could be please give link in docs which exact one i have to use.

stalluri
Valued Contributor
Valued Contributor

@saqib 

AzureAD has OOTB.
Azure provisioning we have to use REST.



Best Regards,
Sam Talluri
If you find this a helpful response, kindly consider selecting Accept As Solution and clicking on the kudos button.

saqib
New Contributor
New Contributor

@stalluri 

Yes we are trying with Azure provisioning using the REST connector , And the problem is on Priv Entitlement. in postman i'm able to provision correctly as im populating all the roledefination details manually.

 

saqib_0-1726210849177.png

 

{ "name": "ResourceGroup",
"connection": "userAuth",
"privilegeEntitlement":{"privEntType":"RoleDefinition","privAttrName":"Roles"},
"url": "https://management.azure.com${entitlementValue.customproperty4}/providers/Microsoft.Authorization/roleAssignments/${UUID.randomUUID().toString()}?api-version=2015-07-01",
"httpMethod": "PUT",
"httpParams": "{ \"properties\": { \"roleDefinitionId\": \"${privEntVal.customproperty4}\", \"principalId\": \"${account.accountID}\" } }",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json"
}

 

Share logs


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

I'm trying to provision for Azure , Not Azure AD.

stalluri
Valued Contributor
Valued Contributor

@saqib 

Try this 
${entitlementValuesObj.customproperty4}  //role Definition Id is not empty
${account.accountID}           // make sure the principal Id  is not empty



Make sure you have values present in entitlement customproperty4 (ID) and this ID should be referred in entitlementtype customproperty4

${privEntVal.customproperty4}

 


Best Regards,
Sam Talluri
If you find this a helpful response, kindly consider selecting Accept As Solution and clicking on the kudos button.