How we can use the AGS web service to add an entitlement to a role?

[PingTai]

How we can use the AGS web service to add an entitlement to a role?

curl -XPOST https://******/aveksa/command.submit?cmd=addEntitlementToRole&role_id=test&ent_id=test

Error 500: Neither role name nor role id were defined in the request

[PingTai]

Currently we follow below steps to do it manually, however it will increase our workload if there are multiple FR and entitlement. We would like to use API or web service to invoke this directly instead of manual work. Kindly advice.

1. Open AGS

2. Go to roles 
3. Again click on Roles

4. Copy paste a Specific one from our excel sheet
5. Click on the role 
6. Go to entitlements Tab 
7. Click Add entitlements 
8. Search the entitlement that we want to map with this particular FR and click the check-box

9. After selecting Click on OK button. 
10. Click on Apply Changes Button

[IanStaines]

Can you provide more information about what version you are on?  

[IanStaines]

Ping,

This feature is not part of the default RSA Identity Governance & Lifecycle product.  It appears to be a value added feature probably from your vendor or VAR.   You may have support for this feature through an extended support agreement outside of the general product.  I suggest you contact your vendor who may be able to direct your question. 

[PingTai]

6.9.1

patch 25

It is our production version.

[PingTai]

Could you help to advice whether below version in our production had include this feature?

6.9.1

patch 25

if not, what we should do for this one? Thanks.

[DianeMccoy]

Hi Ping,

As Ian mentioned, this is not a default RSA Identity Governance & Lifecycle product. So no version or patch has this installed by default. That said, if you go to Admin > Web Services and you see the same information in production as you see in the screenshot you sent us, then that would mean you have it installed. I'm curious as to where you got that screenshot if not from your system.  Do you have a vendor/VAR that you can contact? Our professional services team might also be able to help you out. However, I believe they only work on supported product versions ( 6.9.1 reached end of product support over two years ago (Aug 2017)).

One observation. In your curl command you have 'role_id=test&ent_id=test'. Assuming the AGS web service commands follow the same syntax as the RSA Identity Governance & Lifecycle web service commands, 'id' would refer to the id in the database table where the information is stored and is the unique identifier for the role or entitlement. That means id is always a number. So the word 'test' could be the role and/or entitlement name but it would not be the id.

Regards, Diane

[PingTai]

Thanks Diane for your reply.

Regarding we shared screenshot, we got it from our AGS production. Admin->WebSerivce. We will try to find related vendor/VAR.

for related POST URL:

curl -XPOST https://******/aveksa/command.submit?cmd=addEntitlementToRole&role_id=test&ent_id=test

Based on your advice, it means related role_id and ent_id value should be picked up from AGS database internally, then we can update it directly. Am i correct?

[DianeMccoy]

Hi Ping,

If your production database is an RSA Identity Governance & Lifecycle database, then yes, those IDs come from the internal RSA Identity Governance & Lifecycle database. Since the web service commands in the screenshot are not part of our product I really can't assist on the command usage but that is the direction I would try given the similarity to the default web services commands available in RSA Identity Governance & Lifecycle. 

Regards, Diane