OpenText
OpenText provides a complete and integrated Information Management platform, allowing companies to organize, integrate and protect data and content as it flows through business processes inside and outside the organization.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 388: Supported operations for Users
|
Create User |
POST |
|
Get a user |
GET |
|
Update a user |
PUT |
|
Get all Users |
GET |
|
Delete a User |
DELETE |
Group
Table 389: Supported operations for Groups
|
Create Group |
POST |
|
Get a Group |
DELETE |
|
Get all Group |
GET |
|
Update a Group |
PUT |
| Delete a Group |
DELETE |
Mandatory fields
Users
Groups
User and Groups mapping
The user and Groups mappings are listed in the tables below.
Table 390: User mapping
| id |
id |
| externalId |
externalId |
| userName |
userName |
| name.givenName |
name.givenName |
| name.formatted |
name.formatted |
| name.familyName |
name.familyName |
| displayName |
displayName |
| title |
title |
| userType |
userType |
| locale |
locale |
| timezone |
timezone |
| preferredLanguage |
preferredLanguage |
| emails[].value |
emails[].value |
| emails[].type |
emails[].type |
| phoneNumbers[].value |
phoneNumbers[].value |
| phoneNumbers[].type |
phoneNumbers[].type |
| 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 |
| userExtension.employeeNumber |
userExtension.employeeNumber |
| userExtension.costCenter |
userExtension.costCenter |
| userExtension.organization |
userExtension.organization |
| userExtension.division |
userExtension.division |
| userExtension.department |
userExtension.department |
| userExtension.manager.value |
userExtension.manager.value |
| userExtension.manager.location |
userExtension.manager.$ref |
| password |
password |
| active |
active |
| meta.created |
meta.created |
| meta.lastModified |
meta.lastModified |
Table 391: Group mapping
| id |
id |
| displayName |
displayName |
| GroupExtension.externalId |
externalId |
| GroupExtension.emails[].value |
emails[].value |
| GroupExtension.emails[].type |
emails[].type |
| members[].value |
members[].value |
| members[].type |
members[].type |
| members[].display |
members[].display |
| meta.created |
meta.created |
| meta.lastModified |
meta.lastModified |
Connector limitations
-
Most of the attributes like phoneNumber, addresses, preferredLanguage, timezone, locale takes any junk value due to target API behavior.
JFrog Artifactory
JFrog Artifactory is the single solution for housing and managing all the artifacts, binaries, packages, files, containers, and components for use throughout your software supply chain. JFrog Artifactory serves as your central hub for DevOps, integrating with your tools and processes to improve automation, increase integrity, and incorporate best practices along the way.
Supervisor Configuration Parameters
Supported objects and operations
Users
Table 392: Supported operations for Users
|
Create User |
POST |
| Get User by Id |
GET |
| List Users |
GET |
|
Update user |
PUT |
|
Delete user |
DELETE |
Groups
Table 393: Supported operations for Groups
| Create a group |
POST |
|
Delete a group |
DELETE |
|
Get Group by Id |
GET |
|
List groups |
GET |
|
Update Group |
PUT |
Mandatory Fields
This section lists the mandatory fields required to create a User or Group:
Users
-
userName
-
emails[].value
-
password
Groups
Mappings
The mappings are listed in the tables below.
Table 394: JFrog Artifactory User to SCIM user mapping
| name |
id |
| name |
UserName |
| group |
groups[].value |
| realm |
extension.realm |
| status |
active |
| email |
emails[].value |
Table 395: JFrog Artifactory Group to SCIM group mapping
| name |
id |
| name |
displayName |
| usernames[] |
members[] |
| description |
extension.description |
| realm |
extension.realm |
Connector limitations
- Pagination is not supported in both users and groups endpoints.
- When list of users or groups are retrieved from connector we get limited number of attributes, so not all the attributes in get user by id is supported in get a list of users. Only id, userName, realm, meta are supported in list of users and id, displayName, meta are supported in list of groups, this is because the target system also return limited number of attributes.
- The resources do not have the important meta informations created date and lastModified date.
xMatters
xMatters is a service reliability platform that helps DevOps, SRES, and operations teams automate workflows, ensure infrastructure and applications are always working, and rapidly deliver products at scale. Our code-free workflow builder, adaptive approach to incident management, and real-time performance analytics all support a single goal: the happiness of your customers.
Supervisor Configuration Parameters
Supported objects and operations
Users
Table 396: Supported operations for Users
|
Create |
POST |
| Get User by Id |
GET |
| List Users |
GET |
|
Update user |
PUT |
|
Delete user |
DELETE |
Groups
Table 397: Supported operations for Groups
| Create group |
POST |
|
Delete group |
DELETE |
|
Get Group by Id |
GET |
|
List groups |
GET |
|
Update Group |
PUT |
Roles
Table 398: Supported operations for Roles
| Get Role By Id |
GET |
|
List Roles |
GET |
Mandatory Fields
This section lists the mandatory fields required to create a User or Group:
Users
-
userName
-
name.familyName
-
name.givenName
-
roles[].value
Groups
Mappings
The mappings are listed in the tables below.
Table 399: xMatters User to SCIM user mapping
| id |
id |
| links.self |
profileUrl |
| targetName |
userName |
| firstName |
name.givenName |
| firstName lastName |
name.formatted |
| lastName |
name.familyName |
|
firstName lastName |
displayName |
|
roles[].name |
roles[].display |
|
status |
active |
|
recipentType |
userType |
|
timezone |
timezone |
|
language |
preferredLanguage |
|
whenCreated |
meta.created |
|
whenUpdated |
meta.lastModified |
Table 400: xMatters Group to SCIM group mapping
| id |
id |
| targetName |
displayName |
| status |
extension.active |
| description |
extension.description |
| members[].id |
members[].value |
|
createTime |
meta.created |
|
members[].targetName |
members[].display |
Table 401: xMatters Role to SCIM role mapping
| id |
id |
| name |
role[].name |
Connector limitations
-
List Groups do not support the members Attribute in query attributes.
-
Roles do not support query attribute feature.
-
If invalid Id value is used while deleting Users and Groups, the response has status code 204 due to target behavior.
Discourse
Discourse is the 100% open source discussion platform built for the next decade of the Internet. Use it as a mailing list, discussion forum, long-form chat room, and more! Discourse is a from-scratch reboot, an attempt to reimagine what a modern Internet discussion forum should be today, in a world of ubiquitous smartphones, tablets, Facebook, and Twitter.
Supervisor Configuration Parameters
- Connector name
- Api Key
- Target URL (https://instance_name.discourse.group)
Supported objects and operations
Users
Table 402: Supported operations for Users
|
Create User |
POST |
| Get User by Id |
GET |
| List Users |
GET |
|
Update user |
PUT |
|
Delete user |
DELETE |
Groups
Table 403: Supported operations for Groups
| Create a group |
POST |
|
Delete a group |
DELETE |
|
Get Group by Id |
GET |
|
List groups |
GET |
|
Update Group |
PUT |
Mandatory Fields
This section lists the mandatory fields required to create a User or Group:
Users
-
userName
-
emails[].value
-
displayName
-
password
Groups
Mappings
The mappings are listed in the tables below.
Table 404: Discourse User to SCIM user mapping
|
id |
id |
| username |
UserName |
| name |
displayName |
| active |
active |
| admin |
extension.admin |
| created_at |
meta.Created |
|
name |
name.formatted |
|
emails |
emails[].value |
Table 405: Discourse Group to SCIM group mapping
| name |
id |
| name |
displayName |
| members[].id |
members[].value |
Connector limitations
- Discourse Target System does not return important meta information lastModified for users and created and lastModified for groups.
- In pagination, the records can be returned in multiples of 100 only.
- Modifying the displayName of a group would change its id.
- Specifying the attribute 'members' in Groups LIST will not return the members as getting the members would slow down the LIST request processing as there would be as many number of additional membership requests as the number of groups in the list response are needed due to a target API behavior.
- StartIndex value is ignored in this connector due to the target API behavior (page based).
- Without passing anything in update request body, the update API runs and give the old data.
- In Users/Get user by id, target behaviour which ignores some characters from id. "1cc1" is considered as "1" itself.
- While giving invalid API key, target gives 404 (not found) instead of 401 (unauthorized).
