Additional Configuration Parameters

During an update operation, the SCIM connector skips the defined attributes. For example:

<entry key="skipSchemaAttributes">
   <value>
     <List>
       <String>alias</String>
       <String>groups</String>
     </List>
   </value>
</entry> 

Enables PUT operation for SCIM compliant servers.

<entry key="HttpPatchSupport">
   <value>
      <Boolean>false</Boolean>
   </value>
</entry>

Retrieves defined query attributes during account and group aggregation. For example:

<entry key="queryAccountSchemaAttributes">
 <value>
  <List>
       <String>userName</String>
       <String>urn:scim:schemas:extension:enterprise:1.0:manager</String>
   </List>
 </value>
</entry> 

Note
Specify the fully qualified extended attributes with the associated Resource URN.
For example, the manager attribute defined in urn:scim:schemas:extension:enterprise is fully encoded as urn:scim:schemas:extension:enterprise:manager.

Provides the list of fully qualified extended attributes with the associated Resource URN. For example:

<entry key="extensionSchemaAttributes">
 <value>
   <List>
       <String>urn:scim:schemas:extension:enterprise:manager</String>
   </List>
 </value>
</entry> 

Defines mapping of connector schema attributes with SCIM schema attributes. For example:

<entry key="scimAttrMapping">
  <value>
    <Map>
       <entry key="name">
         <value>
           <Map>
             <entry key="familyName" value="familyName"/>
             <entry key="formattedName" value="formatted"/>
             <entry key="givenName" value="givenName"/>
           </Map>
         </value>
       </entry>
    </Map>
  </value>
</entry> 

In the previous example, <entry key="name"> is the SCIM complex attribute created with subAttributes familyName, formatted, and givenName. These are mapped to the familyName, formattedName, and givenName connector schema attributes respectively.

Contains the alg attribute (algorithm that is used for signing the JWT assertion). Must be the same algorithm used for generating the private key.

<entry key="oAuthJwtHeader"> 
  <value> 
    <Map> 
      <entry key="alg" value="RS256"/> 
    </Map> 
  </value> 
</entry> 

If required, you can provide additional header attributes in this map.

Contains the aud (audience) attribute, exp (expiry of the JWT assertion), iss (issuer), sub (subject) attributes.

<entry key="oAuthJwtPayload"> 
  <value> 
    <Map> 
     <entry key="aud" value=""/> 
     <entry key="exp" value="15f"/> 
     <entry key="iss" value=""/> 
     <entry key="sub" value=""/> 
   </Map> 
  </value> 
</entry>

If required, you can provide additional payload attributes in this map.