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
Connector limitations
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 |
-
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