Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
I have a requirement to tag a large number of privileged entitlements for a client's GCP environment, and am using schema-based entitlement import to do so. I discovered that it is possible to introduce duplicates via the schema-based entitlement imp...
Hello,My customer uses Bitbucket code repo, which is an Atlassian UI over Git. They have asked about managing that via a Saviynt connector, but I don't see any reference to it in the documentation, and a quick search here turned up no results. I assu...
Hi,I've searched the docs and forums and have not found where the "To:" email for the "...(ApplicationDataImportJob) has been blocked and skipped" notifications is set. I am receiving this notification to my email, and the "From:" address is the one ...
We need someone on the Saviynt side to confirm for us that outbound requests are allowed on the Saviynt application side. We need to make sure it's allowed to reach out to the SCIM application over ports 8080 - HTTP and 8443 - HTTPS . The reachabili...
The GCP job is taking a very long time to run. We wanted to limit the entitlement types reconciled. The documentation here at Importing Data for the GCP Connector states that you can limit the entitlement types by "Sample Import Config JSON to impor...
I deleted line 3 (though I saw nothing there), and reperformed the import. My test field (customproperty30) was updated accordingly, but the ENTITLEMENTID was not.
I performed a repeat of the import with an 'operation' column added with the action 'Update' specified. The above error, "ERROR column count mismatch" did not re-occur, but it did not populate the ENTITLEMENTID. It did update another field I used for...
I just re-performed a test of uploading a new entitlement to the endpoint with an 'ENTITLEMENTID' (spelling as specified in the Schema in the Data Analyzer). These are the attributes in my SAV file:securitysystems,endpoints,entitlementtype,entitlemen...
Hi, RushikeshI supplied the operation (update) and the entitlement value key in the SAV/CSV files and ran a single test, which created another duplicate entitlement. Can you confirm that there's no way to prevent this from happening when using schema...
