SCIM 2.0 Driver Shim

Idea ID 2784170

SCIM 2.0 Driver Shim

IT is moving more and more to a hybrid and cloud based approach. To provision identities in a cloud based environment SCIM 2.0 is now a days becoming a major player:

http://www.simplecloud.info/#Implementations2

The fact that SCIM 2.0 is extensible makes it a future proof standard, that was lacking in SCIM 1.0.

A lot of competitors (Oracle, Microsoft, Okta, One Identity etc.) already have a connector available. To catch this running train Micro Focus Identity Manager should jump a board by developing a SCIM 2.0 Driver Shim for IDM.
6 Comments
Visitor.
Please also take into account that the driver can be a SCIM 2.0 endpoint on the publisher channel listening for pushed events. Note that the publisher channel shoud be equipped with an oAuth2 server component as all SCIM clients nowadays use oAuth2 as preferred authentication protocol.
Absent Member.
Absent Member.
I couldn't agree more with this suggestion. We have a high-profile integration that we want to do with IDM but the vendor only accepts SCIM 2.0 implemntation. As such, we are forced to do a significant customization of the REST driver. This does not make IDM look good in the eyes of our leadership. 😞
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Accepted

A new SCIM driver is under development. The first release is aimed at supporting client mode over the subscriber channel.

A beta is tentatively scheduled for mid-June. If you are interested in participating in the program, please drop a note to abhishek.prasad@microfocus.com.

Super Contributor.
Super Contributor.

@Abhishek Prasad  in wonder what is different between Generic NEIQ REST Driver or SCIM 2.0?  it's just a JSON payload which is different in a traditional NetIQ REST connector.

 

We have written tons of SCIM intgr using NETIQ Rest Driver, and don't understand why people are asking SCIM? 🙂

 

just a thought!

/Maqsood

 

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

@maqsood Technically, yes. REST driver can be used to connect to SCIM systems by building integration. Having said that,  this approach forces partners towards custom development and maintenance for a protocol that is standardized – which of course you would be aware considering the multiple integration your team has developed.

Super Contributor.
Super Contributor.

@Abhishek Prasad  good. still being standardized scim 2.0, in our experiences, vendors are just doing their custom versions of SCIM no following strict to 2.0, so customization in payloads will certainly be on your top of "customization of scim" feature requests  once you release 🙂

 

NetIQ REST connector is very flexible apart from few limitations, like HTTP methods support (not all HTTP methods) are supported, nothing wrong with NetIQ REST connector, it just nasty developers out there implement APIS wildly not following any standards.

 

 

 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.