Mandatory fields
SugarCRM is a customer relationship management (CRM) system. It allows users to manage sales-force automation, marketing campaigns, customer support, collaboration, mobile CRM, social CRM, and reporting.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 152: Supported operations for Users
|
Create |
POST |
|
Update |
PUT |
|
Delete |
DELETE |
|
Get user by Id |
GET |
|
Get all users |
GET |
Groups
Table 153: Supported operations for Groups
| Create |
POST |
| Update |
PUT |
| Delete |
DELETE |
| Get all groups |
GET |
|
Get all groups by Id |
GET |
Users
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 154: User mapping
| Id |
id |
| UserName |
user_name |
|
Title |
title |
|
PreferredLanguage |
preferred_language |
|
name.FirstName |
first_name |
| name.LastName |
last_name |
| name.Formatted |
full_name |
| Address.StreetAddress |
address_street |
| Address.Region |
address_city |
| Address.Country |
address_country |
| Address.PostalCode |
address_postalcode |
| Emails.value |
email[0].email_address |
|
Active |
status.Value == "Active" |
|
Groups[].display |
team_name[].name |
|
Groups[].value |
team_name[].id |
|
PhoneNumbers[].Value |
phone_home |
|
PhoneNumbers[].Value |
phone_mobile |
|
PhoneNumbers[].Value |
phone_work |
|
Meta.Created |
date_entered |
|
Meta.LastModified |
date_modified |
Table 155: Group mapping
| id |
id |
| displayName |
name |
| Meta.created |
date_entered |
| Meta.lastModified |
date_modified |
Connector limitations
-
Creation of a duplicate user returns the following status code:
- A CRUD operation on Users and Groups can be performed only by users with Admin credentials.
- Multiple groups can be created with same name.
-
Group memberships cannot be added, retrieved, or modified using API calls.
-
Cloud application allows creation of a group without the Name being specified.
User and Group mapping
SugarCRM is a customer relationship management (CRM) system. It allows users to manage sales-force automation, marketing campaigns, customer support, collaboration, mobile CRM, social CRM, and reporting.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 152: Supported operations for Users
|
Create |
POST |
|
Update |
PUT |
|
Delete |
DELETE |
|
Get user by Id |
GET |
|
Get all users |
GET |
Groups
Table 153: Supported operations for Groups
| Create |
POST |
| Update |
PUT |
| Delete |
DELETE |
| Get all groups |
GET |
|
Get all groups by Id |
GET |
Mandatory fields
Users
Groups
The user and group mappings are listed in the tables below.
Table 154: User mapping
| Id |
id |
| UserName |
user_name |
|
Title |
title |
|
PreferredLanguage |
preferred_language |
|
name.FirstName |
first_name |
| name.LastName |
last_name |
| name.Formatted |
full_name |
| Address.StreetAddress |
address_street |
| Address.Region |
address_city |
| Address.Country |
address_country |
| Address.PostalCode |
address_postalcode |
| Emails.value |
email[0].email_address |
|
Active |
status.Value == "Active" |
|
Groups[].display |
team_name[].name |
|
Groups[].value |
team_name[].id |
|
PhoneNumbers[].Value |
phone_home |
|
PhoneNumbers[].Value |
phone_mobile |
|
PhoneNumbers[].Value |
phone_work |
|
Meta.Created |
date_entered |
|
Meta.LastModified |
date_modified |
Table 155: Group mapping
| id |
id |
| displayName |
name |
| Meta.created |
date_entered |
| Meta.lastModified |
date_modified |
Connector limitations
-
Creation of a duplicate user returns the following status code:
- A CRUD operation on Users and Groups can be performed only by users with Admin credentials.
- Multiple groups can be created with same name.
-
Group memberships cannot be added, retrieved, or modified using API calls.
-
Cloud application allows creation of a group without the Name being specified.
Connector limitations
SugarCRM is a customer relationship management (CRM) system. It allows users to manage sales-force automation, marketing campaigns, customer support, collaboration, mobile CRM, social CRM, and reporting.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 152: Supported operations for Users
|
Create |
POST |
|
Update |
PUT |
|
Delete |
DELETE |
|
Get user by Id |
GET |
|
Get all users |
GET |
Groups
Table 153: Supported operations for Groups
| Create |
POST |
| Update |
PUT |
| Delete |
DELETE |
| Get all groups |
GET |
|
Get all groups by Id |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 154: User mapping
| Id |
id |
| UserName |
user_name |
|
Title |
title |
|
PreferredLanguage |
preferred_language |
|
name.FirstName |
first_name |
| name.LastName |
last_name |
| name.Formatted |
full_name |
| Address.StreetAddress |
address_street |
| Address.Region |
address_city |
| Address.Country |
address_country |
| Address.PostalCode |
address_postalcode |
| Emails.value |
email[0].email_address |
|
Active |
status.Value == "Active" |
|
Groups[].display |
team_name[].name |
|
Groups[].value |
team_name[].id |
|
PhoneNumbers[].Value |
phone_home |
|
PhoneNumbers[].Value |
phone_mobile |
|
PhoneNumbers[].Value |
phone_work |
|
Meta.Created |
date_entered |
|
Meta.LastModified |
date_modified |
Table 155: Group mapping
| id |
id |
| displayName |
name |
| Meta.created |
date_entered |
| Meta.lastModified |
date_modified |
-
Creation of a duplicate user returns the following status code:
- A CRUD operation on Users and Groups can be performed only by users with Admin credentials.
- Multiple groups can be created with same name.
-
Group memberships cannot be added, retrieved, or modified using API calls.
-
Cloud application allows creation of a group without the Name being specified.
Oracle IDCS
Oracle IDCS is a cloud-based identity management service that integrates with existing systems and directories. Users can develop, access and deploy their applications from one platform. It works with both cloud and on-premises applications.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 156: Supported operations for Users
|
Create |
POST |
|
Update |
PUT |
|
Delete |
DELETE |
|
Get all users |
GET |
|
Get user by id |
GET |
| Get users with Pagination |
GET |
Groups
Table 157: Supported operations for Groups
|
Create |
POST |
|
Update |
PUT |
|
Delete |
DELETE |
|
Get |
GET |
|
Get |
GET |
Mandatory fields
Users
-
userName
-
emails.value
-
name.familyName
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 158: User mapping
| Id |
id |
| userName |
userName |
| externalId |
externalId |
| name.givenName |
name.givenName |
|
name.familyName |
name.familyName |
| name.middleName |
name.middleName |
| name.formatted |
name.formatted |
| name.honorificPrefix |
name.honorificPrefix |
| name.honorificSuffix |
name.honorificSuffix |
| displayName |
displayName |
| nickName |
nickName |
| emails.value |
email.value |
| emails.type |
email.type |
| emails.primary |
email.primary |
| addresses.formatted |
addresses.formatted |
| addresses.streetAddress |
addresses.streetAddress |
| addresses.locality |
addresses.locality |
| addresses.region |
addresses.region |
| addresses.postalCode |
addresses.postalCode |
| addresses.country |
addresses.country |
| addresses.type |
addresses.type |
| phoneNumbers.value |
phoneNumbers.value |
| phoneNumbers.type |
phoneNumbers.type |
| phoneNumbers.primary |
phoneNumbers.primary |
| password |
password |
| profileUrl |
profileUrl |
| title |
title |
| userType |
userType |
| preferredLanguage |
preferredLanguage |
| locale |
locale |
| timezone |
timeZone |
| active |
active |
| entitlements.value |
entitlements.value |
| entitlements.display |
entitlements.display |
| entitlements.type |
entitlements.type |
| roles.value |
roles.value |
| roles.display |
roles.display |
| roles.type |
roles.type |
| groups.value |
groups.value |
|
groups.display |
groups.display |
|
extension.organization |
extension.organization |
|
extension.division |
extension.division |
|
extension.department |
extension.department |
|
extension.manager.value |
extension.manager.value |
|
extension.manager.displayName |
extension.manager.displayName |
|
extension.costCenter |
extension.costCenter |
|
extension.employeeNumber |
extension.employeeNumber |
|
meta.created |
meta.created |
|
meta.lastModified |
meta.lastModified |
Table 159: Group mapping
| id |
id |
| displayName |
displayName |
| Members.value |
members.value |
| Members.display |
members.display |
| extension.externalId |
extension.externalId |
| extension.description |
extension.description |
|
meta.created |
meta.created |
|
meta.lastModified |
meta.lastModified |
Connector limitations
-
Oracle IDCS does not validate the values provided for the roles in the user request and the same is getting assigned to the user. No validation is performed for the type, value properties for the roles. Same is the case with entitlements.
-
Groups will not be returned with the create user response.
-
Sub-Groups cannot be added in Group Memberships.