User and Group mapping
Egnyte lets users store files on either a company’s existing data center infrastructure or in the cloud. It can be integrated with the cloud, storage, devices, and business applications to let you control data with your current hardware.
Supervisor configuration parameters
To configure the connector, following parameters are required:
To get the Client_id
- Login to the Egnyte cloud application.
-
Register an application under My API Keys menu. Registered Application will have an API key that can be used as Client_Id.
Supported objects and operations
Users
Table 142: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get user by Id |
GET |
Get all users |
GET |
Get all users with pagination |
GET |
Groups
Table 143: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get all groups |
GET |
Get all groups with pagination |
GET |
Mandatory fields
Users
Groups
The user and group mappings are listed in the tables below.
Table 144: User mapping
Id |
Id |
externalId |
externalId |
userName |
userName |
Name.FamilyName |
name.FamilyName |
Name.givenName |
name.givenName |
Name.Formatted |
name.Formatted |
DisplayName |
name.Formatted |
email.value |
email |
Active |
active |
userType |
userType |
EnterpriseExtension.authType |
authType |
Groups.DisplayName |
groups.DisplayName |
Groups.Value |
groups.Value |
Created |
createdDate |
LastModified |
lastModificationDate |
Table 145: Group mapping
Id |
id |
displayName |
displayName |
members.value |
members.value |
members.display |
members.display |
Connector limitations
- The Role object type is not supported by cloud application for trial account. Hence, the connector does not support the role endpoint.
Connector limitations
Egnyte lets users store files on either a company’s existing data center infrastructure or in the cloud. It can be integrated with the cloud, storage, devices, and business applications to let you control data with your current hardware.
Supervisor configuration parameters
To configure the connector, following parameters are required:
To get the Client_id
- Login to the Egnyte cloud application.
-
Register an application under My API Keys menu. Registered Application will have an API key that can be used as Client_Id.
Supported objects and operations
Users
Table 142: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get user by Id |
GET |
Get all users |
GET |
Get all users with pagination |
GET |
Groups
Table 143: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get all groups |
GET |
Get all groups with pagination |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 144: User mapping
Id |
Id |
externalId |
externalId |
userName |
userName |
Name.FamilyName |
name.FamilyName |
Name.givenName |
name.givenName |
Name.Formatted |
name.Formatted |
DisplayName |
name.Formatted |
email.value |
email |
Active |
active |
userType |
userType |
EnterpriseExtension.authType |
authType |
Groups.DisplayName |
groups.DisplayName |
Groups.Value |
groups.Value |
Created |
createdDate |
LastModified |
lastModificationDate |
Table 145: Group mapping
Id |
id |
displayName |
displayName |
members.value |
members.value |
members.display |
members.display |
- The Role object type is not supported by cloud application for trial account. Hence, the connector does not support the role endpoint.
SugarCRM
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 146: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get user by Id |
GET |
Get all users |
GET |
Groups
Table 147: 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 148: 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 149: 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.
Supervisor configuration parameters
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.
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 146: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get user by Id |
GET |
Get all users |
GET |
Groups
Table 147: 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 148: 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 149: 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.