Cloud / G Suite Connector by Microsoft - Provision user custom schema fields

Question

Cloud / G Suite Connector by Microsoft - Provision user custom schema fields

Fernando Almeida 106

The documentation for the connector does not provide any explicit reference on how one could Mal an AAD user standard or extension properties to user custom schemas.

Given that JSONPath seems to be used in the object mappings and definitions I naively assumed that using a targetAttributeName the followed the convention "customSchemas.<Schema name>.<Field name>" and set the appropriate data type would allow me to map any required values.
I'm currently assuming that for some reason this is not supported because it's not documented even though it does not seem that hard to add support this.
Can anyone please shed some light on this matter if I'm wrongly assuming this is unsupported by the connector?

Thanks I'm advance,
Fernando

Accepted answer

0 additional answers

Your answer

Answer 1

Danny Zollner 10,801 Microsoft Employee Moderator

You are correct that this is unsupported. This is mentioned in our documentation here: https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/customize-application-attributes#editing-the-list-of-supported-attributes

Our GSuite connector uses a proprietary GSuite API, and we in most cases do not support using custom attributes with connectors based on proprietary APIs. We do support custom attributes for any SCIM 2.0 applications, but that isn't helpful here, unfortunately.

Fernando Almeida 106 Reputation points

2022-09-03T09:04:03.647+00:00

Thanks for the succinct and explicitly referenced clarification.

I get it that you're using a proprietary API but in that respect I don't get why y'all didn't extend support for "fake discoverability" implicitly using the Schemas API or could not simply rely in JSONPath custom expressions at the users's own risk to allow the creation of mapping against dynamic fields. Bear in mind that custom schemas is clearly defined as an optional attribute that is part of the user schema for Google and this could have easily been interpreted by whomever developed the app as a Dictionary<string, Dictionary<string,object>> such that a specific JSONPath expression could be evaluated against even without knowledge or assumption of the registered custom schemas from the Google Admin Schemas API.

Ultimately, if I'm need of mapping these I would need to create a standalone script to do this. And if I have to go through such effort to be able to use custom schema fields if I require them bad then I see no point in using this app as I could just as easily implement the mapping expressions for other attributes in the developed code.

Share via

Cloud / G Suite Connector by Microsoft - Provision user custom schema fields

0 additional answers

Your answer