In order to create the HTTP Operations, you can update your source with the below configuration. This time is simple and so is the implementation.ħ. A more or less complete connector is going to depend on your needs, on the particular use case. For instance, we're not even going to bother to implement "Add Entitlement" and that's fine, because we only want to remove entitlements. We're not going to implement all connector operations. This is what we're going to ultimately certify. The concept is simple: we're aggregating accounts from IdentityNow's active identities and each one of them has a single and exclusive entitlement: itself. It's a way to check who's active in the system, regardless of their permissions, and if somebody who shouldn't be there is present, trigger the leaver process to strip off permissions, disable accounts, etc. The purpose of this loopback connector is using it on certifications so the revocation of an identity changes that identity's lifecycle state to inactive and triggers a leaver event. Loopback connector for identity certifications Description As a bonus, I'll also share with you a connector to manage IdentityNow's capabilities like any other managed system. I'm going to walk you through the process of building a loopback connector to certify identities instead of regular access. There's a lot interesting use cases you can accomplish by using this concept since you can access identity, account, entitlement and activity data to name a few. Loopback is not a special type of connector but a web services connector pointing to IdentityNow's API. This time I want to introduce you to the concept of loopback connectors. Well, this time I'm not going to talk about ETS and Pipedream, but we'll get back there, no doubt.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |