Connector limitations
Dropbox offers secure file sharing and storage. It helps users manage sharing capabilities with groups and external collaborators through central folders with granular permissions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 55: 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 56: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get all groups |
GET |
Get group by Id |
GET |
Get groups with pagination |
GET |
Roles
Table 57: Supported operations for Roles
Get all roles |
GET |
Get role by Id |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 58: User mapping
id |
profile.team_member_id |
externalId |
profile.external_id |
userName |
profile.email |
name.familyName |
profile.name.surname |
name.givenName |
profile.name.given_name |
name.formatted |
profile.name.display_name |
displayName |
profile.name.display_name |
emails[0].value |
profile.email |
active |
profile.status[".tag"] |
groups |
profile.groups |
roles |
role[".tag"] |
meta.created |
profile.joined_on |
Table 59: Group mapping
id |
group_id |
displayName |
group_name |
members[].value |
members[].profile.team_member_id |
members[].display |
members[].profile.name.display_name |
enterpriseExtension.externalId |
group_external_id |
meta.created |
created |
-
The LastModified date is not applicable for Groups.
- Both created and lastModified dates are not applicable for Users.
-
Invalid Target URL returns the below mentioned status code and error message.
- Status code: 500
- Error message: There was an issue processing this request error.
-
User's role cannot be updated.
-
The user cannot be set as active while performing create or update.
-
The information about groups will not be present in the Create user response.
-
The Dropbox user statuses active and invited are considered as active in the connector.
-
APIs are not available to retrieve roles from Dropbox. Hence, the endpoints of the connector's roles provide predefined set of roles.
-
Deleted members cannot be added to a group. In a request to add multiple members to a group, if any user is deleted (members_not_in_team), then the entire request is not carried out.
-
The userName property for user is read-only. However, this can be updated by updating the emails → value. The emails → value has been mapped against userName.
-
Dropbox returns error 500 without any message being shown, on cursor pagination with cursor length equal to 1. The same is observed when trying to update a deleted group. In this case, the connector returns the following error code and message:
- Error Code: 400
- Error message: Error occurred.
Crowd
Crowd is a single sign-on software that lets your system administrator connect multiple applications to one user login and password. Users only need one user ID and password to access any connected platform.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 60: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Users |
GET |
Get User by Id |
GET |
Get All Users with pagination |
GET |
Groups
Table 61: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Groups |
GET |
Get Group by Id |
GET |
Get All Groups with pagination |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mapping is listed in the table below.
Table 62: User mapping
Id |
name |
userName |
name |
password |
password |
active |
active |
givenName |
first-name |
familyName |
last-name |
displayName |
display-name |
Formatted |
display-name |
email.value |
email |
Created |
createdDate |
LastModified |
lastModified |
Table 63: Group mapping
Id |
name |
GroupName |
name |
Active |
active |
Description |
description |
members.value |
members.name |
Connector limitations
-
Crowd application does not have the ID field for Users and Groups. User name is considered as the userId, and the group name is considered as groupId.
-
Crowd cloud application does not have a created date and modified date for Groups.
-
UserName and GroupName must be used as a single term as the usage is same for userId and groupId.
-
UserName cannot be updated because it is used as an Id in cloud application.
-
DisplayName of Groups cannot be updated as required by the cloud application.
- The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID
Supervisor configuration parameters
Crowd is a single sign-on software that lets your system administrator connect multiple applications to one user login and password. Users only need one user ID and password to access any connected platform.
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 60: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Users |
GET |
Get User by Id |
GET |
Get All Users with pagination |
GET |
Groups
Table 61: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Groups |
GET |
Get Group by Id |
GET |
Get All Groups with pagination |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mapping is listed in the table below.
Table 62: User mapping
Id |
name |
userName |
name |
password |
password |
active |
active |
givenName |
first-name |
familyName |
last-name |
displayName |
display-name |
Formatted |
display-name |
email.value |
email |
Created |
createdDate |
LastModified |
lastModified |
Table 63: Group mapping
Id |
name |
GroupName |
name |
Active |
active |
Description |
description |
members.value |
members.name |
Connector limitations
-
Crowd application does not have the ID field for Users and Groups. User name is considered as the userId, and the group name is considered as groupId.
-
Crowd cloud application does not have a created date and modified date for Groups.
-
UserName and GroupName must be used as a single term as the usage is same for userId and groupId.
-
UserName cannot be updated because it is used as an Id in cloud application.
-
DisplayName of Groups cannot be updated as required by the cloud application.
- The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID
Supported objects and operations
Crowd is a single sign-on software that lets your system administrator connect multiple applications to one user login and password. Users only need one user ID and password to access any connected platform.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Users
Table 60: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Users |
GET |
Get User by Id |
GET |
Get All Users with pagination |
GET |
Groups
Table 61: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Groups |
GET |
Get Group by Id |
GET |
Get All Groups with pagination |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mapping is listed in the table below.
Table 62: User mapping
Id |
name |
userName |
name |
password |
password |
active |
active |
givenName |
first-name |
familyName |
last-name |
displayName |
display-name |
Formatted |
display-name |
email.value |
email |
Created |
createdDate |
LastModified |
lastModified |
Table 63: Group mapping
Id |
name |
GroupName |
name |
Active |
active |
Description |
description |
members.value |
members.name |
Connector limitations
-
Crowd application does not have the ID field for Users and Groups. User name is considered as the userId, and the group name is considered as groupId.
-
Crowd cloud application does not have a created date and modified date for Groups.
-
UserName and GroupName must be used as a single term as the usage is same for userId and groupId.
-
UserName cannot be updated because it is used as an Id in cloud application.
-
DisplayName of Groups cannot be updated as required by the cloud application.
- The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID