Hi all,

Imagine that I have a customer with Verify SaaS and wants do provisioning accounts into onpremise application that can expose APIRest to be called to create, update and suspend users.  How can I integrate them, using SDI and developing a adapter or there is another approach?

Regards,

Rodrigo

Hi Rodrigo, 
Yes you can provision to onprem ldap targets using Verify Bridge for Provisioning. Please see this doc, very well explained with instructions. 
https://docs.verify.ibm.com/verify/docs/on-premises-provisioning-lifecycle-ldap-directory

If the application supports SCIM via restapi then we can support using the bridge for provisioning to our Verify Directory Server (software or container) and use the Verify Directory Integrator SCIM container as the interface for your application from scim to ldap and then bridge for sync back to verify to update the users accordingly. 
https://www.ibm.com/docs/en/vdi/10.0.0?topic=kubernetes-creating-scim-container
https://www.ibm.com/docs/en/vdi/10.0.0?topic=server-system-cross-domain-identity-management

If the on-prem application only supports RESTAPI then you should be able to call the Verify SaaS APIs directly, if they want to make only calls on-prem then a proxy will need to be created with Directory Integrator.
Hopefully this helps!

Hi,

There is an upcoming (low code/no-code), NodeJS based Adapter studio tool(kit) . Probably still in Beta but soon to be released. Perhaps R. Graham has a better view on this.  Directory integrator and corresponding framework and method for creating adapters helps also with some of the logic and complexity one should not underestimate.  The mapping from the IGA objects into a target application resources (provisioning actions, but also the inverse mapping from resources to (Verify) permissions , account objects (account synchronisation aka recon) should be considered.  Integrations between different technologies , including the domain logic and the mapping is still the most challenging part.

There is a SCIM (Directory integrator) based adapter that can be used with Verify SaaS (for on-prem SCIM provisioning). SCIM v2 is "standardised" on a number of IAM resources (at the target) and is HTTP REST API based. If your target is not using a "standardised" interface, an integration will have to be build. Directory integrator has a whole set of connectors but building an adapter has a learning curve. Maybe  the new tool will attract more developers.