Majesco is the leading software partner to both the P&C and L&A insurance markets for modernization and optimization of their businesses.

Supervisor configuration parameters

To configure the connector, following parameters are required:

• Connector name

• Client Id for the API client

• Client Secret for the API client

• Customer Key

• Target URL (https://instance_name.majesco.com)

• Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details)

Supported objects and operations

Users

Table 380: Supported operations for Users

Operation	VERB
Create User	POST
Get User by Id	GET
List Users	GET
Update User	PUT

Roles

Table 381: Supported operations for Roles

Operation	VERB
Get Role by Id	GET
Create Roles	POST
List Roles	GET
Update Role	PUT

Mandatory fields

Users

• userName

• displayName

• emails[].value

Roles

• name

User and Role mapping

The user mappings are listed in the tables below.

Table 382: User mapping

SCIM User	Majesco User
Id	id
userName	userid
name.Formatted	name
displayName	name
active	status
emails[].value	email
extension.customerCode	customercode
phoneNumbers[].value	phoneno
extension.domain	domain
extension.isExternalUser	isexternaluser
extension.isServiceUser	isserviceuser
extension.isUnlock	isunlock
extension.linkedUserId	linkeduserid
extension.sourceIdentityStoreName	sourceidentitystorename
extension.suspended	suspended
meta.Created	createdate
meta.LastModified	modifieddate
roles[].value	userRoles[].id
roles[].display	userRoles[].rolename
extension.applications	userRoles[].rolename

Table 383: Role mapping

SCIM Role	Majesco Role
Id	id
name	rolename
roleType	roletype
description	roledescription
parentRoles[].value	parentroleslist[].id
parentRoles[].display	parentroleslist[].rolename
childRoles[].value	childroleslist[].id
childRoles[].display	childroleslist[].rolename
meta.Created	createddate
meta.LastModified	modifieddate
members[].value	roleMembers[].id
members[].display	roleMembers[].name

Connector limitations

• Unless modified explicitly, the User resource will not have lastModified value under meta.
• Due to target behavior, it is not possible to disassociate parent roles from a role, however, more roles can be assigned as parent roles.
• DELETE is not supported in the connector, instead UPDATE can be used for inactivating a user. Delete is not supported because the inactivated user at target is still returned in the LIST APIs, which would make data inconsistent at the SCIM client.
• The assignment operations under roles or users would consider only integer valued data due to target API behavior.
• Target API follows PUT REPLACE for update, and hence attributes not passed will get removed from the resource.

• Due to the target behavior, it is not possible to remove all roles associated with a user as well as to remove all users under a role.