Entitlement and AccountName parameters for GrantAccessJSON and RevokeAccessJSON of DB connector

[sk]

Team,

Can anyone help me with the right parameters I can use in GrantAccessJSON & RevokeAccessJSON of DB connector?

We tried below parameters combination for entitlement and account respectively

1. ${task.entitlement_valuekey.entitlement_value}, ${task.ACCOUNTNAME}
2. ${task.entitlement_valuekey.entitlement_value}, ${task.accountName}
3. ${task.entitlement_valuekey.entitlement_value},  ${accountName}
4. ${entitlement_value}, ${accountname}
5. ${entitlement_value}, ${accountName}

Also as per connector documentation(https://saviynt.freshdesk.com/support/solutions/articles/43000617705-database-connector-guide) task is something exposed as binding variable but looks like it is not working.

Example I tried task.accountName in CreateAccountJSON which failed with null pointer exception but once I changed it to ${accountName} it started working.

Now I facing issue in finding right parameters for GrantAccessJSON & RevokeAccessJSON 

Can anyone help me in finding right parameters?

[rushikeshvartak · Accepted solution]

Sample JSON with variables

{ "Database Roles" : ["GRANT \"${task.entitlement_valueKey.entitlement_value}\" TO \"${accountName}\" "] }

Here Database Roles is Entitlement Type Name. 

Please share your JSON if you still facing issue. 

[sk]

Thanks Rushikesh

changing the case of k to K in parameter ${task.entitlement_valueKey.entitlement_value} worked.

So final parameters that are worked

entitlement: ${task.entitlement_valueKey.entitlement_value} 

account: ${accountName}

I am not sure if Saviynt team is watching this thread or not. But just one suggestion is that It would be great if the FD documentation(https://saviynt.freshdesk.com/support/solutions/articles/43000617705-database-connector-guide) is updated with right parameters if they are case sensitive. Right now examples given in this document are not working unless we modify the case as mentioned here.

[NageshK]

Hi SK,

We are indeed watching! Thanks for the suggestion. Duly noted and passed on to the documenation team for correction.

Thanks,

Nagesh K