We need to extract the site roles from an on-prem application and use it as an entitlement, however, there is no API endpoint available to extract that particular attribute. As a workaround, the app owner suggested that they can create a powershell script to define the site roles and have ISC extract it. Is this possible? If so, could you share the high level steps on how to achieve it.
@jasmedina
Use powershell script to extract both accounts and entitlements from on-prem application as a csv file, then create source as delimited type on ISC.
Hi @Anshu_Kunal! If I am understanding it correctly, the powershell script should be stored as a csv file and use that file to upload in the Delimited Type source? Is that correct?
The ps script will extract the accounts and access information of the identities from onprem and generates a csv.
Does this mean that the powershell script should generate the csv that lists all the roles I need? Currently we have the script to print all the roles
# Define the available site role
site_roles = [
"Creator",
"Explorer",
"ExplorerCanPublish",
"Viewer",
"Unlicensed"
]
return site_roles
if __name__ == "__main__":
# List all available site roles
roles = get_site_roles()
print("Available Site Roles:")
for role in roles:
print(role)
Hi @jasmedina ,
The PowerShell or Python script must extract all user account information, including access details, and generate a CSV file for use in account aggregation within ISC.
If you have an script that generates access information only that you can use for entitlement aggregation.
Hi @gourab we were able to extract all user accounts information via the web service connector. We would need these site roles to assign as an access profile to user during provisioning and access requests. Do we still need to include the accounts information in the script or just the site roles name would be enough? Sorry for the questions as this is my 1st time implementing this
Hi @jasmedina
If the source has already been implemented via the Web Service connector, there is no need to generate CSV files. The generation of CSV files for account aggregation is only necessary for delimited sources.
In your Web Service connector configuration, follow these steps:
Navigate to the Account schema and ensure that the schema is correct. Identify the attributes that define access and entitlements, and mark them as entitlements.
In the source configuration, add all related operations, such as account aggregation and entitlement aggregation.
Aggregate the accounts. As you have marked the entitlements in step 1, all entitlements will appear in the entitlements tab.
Mark the entitlements as requestable. They will then be available for access requests through the request center.