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 400: Supported operations for Users
Create |
POST |
Get User by Id |
GET |
List Users |
GET |
Update user |
PUT |
Delete user |
DELETE |
Groups
Table 401: Supported operations for Groups
Create group |
POST |
Delete group |
DELETE |
Get Group by Id |
GET |
List groups |
GET |
Update Group |
PUT |
Roles
Table 402: 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 403: 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 404: 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 405: 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 406: Supported operations for Users
Create User |
POST |
Get User by Id |
GET |
List Users |
GET |
Update user |
PUT |
Delete user |
DELETE |
Groups
Table 407: 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 408: 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 409: 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).
Testrail
TestRail is a web-based test case management tool. It is used by QA engineers, developers, and team leads to manage, track, and organize software testing efforts. TestRail allows team members to design test cases, organize test suites, execute test runs, and track their results, all from a modern and easy-to-use web interface. This article will give you an overview of the core features and workflows in TestRail that you can use to streamline your testing and deliver high-quality releases.
Supervisor Configuration Parameters
Supported objects and operations
Users
Table 410: Supported operations for Users
Create User |
POST |
Get User by Id |
GET |
List Users |
GET |
Update user |
PUT |
Groups
Table 411: 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
Groups
Mappings
The mappings are listed in the tables below.
Table 412: TestRail User to SCIM user mapping
id |
id |
name |
UserName |
group_ids |
groups |
is_admin |
extension.admin |
is_active |
active |
email |
emails[].value |
Table 413: TestRail Group to SCIM group mapping
id |
id |
name |
displayName |
user_ids |
members[].value |
Connector limitations
- Deleting of User is not supported.
ChipSoft
ChipSoft contributes to greater patient safety and more efficiency by develops cutting-edge software for healthcare professionals.
Offering fully integrated EMR/EHR solution for both individual organisations as well as organisations operating within the entire chain of care, ChipSoft is the market leader in Netherlands and in expansion across Europe.
Supervisor Configuration Parameters
-
Connector name
-
Target URL
Supported objects and operations
Users
Table 414: Supported operations for Users
Create User |
POST |
Get User by Id |
GET |
List Users |
GET |
Update user |
PUT |
Login Groups
Table 415: Supported operations for Login Groups
Get Login Group by Id |
GET |
List users |
GET |
User Groups
Table 416: Supported operations for User Groups
Get User Group by Id |
GET |
List User Groups |
GET |
Mandatory Fields
This section lists the mandatory fields required to create a User or Group:
Users
- ldap
- userName
- displayName
- active
- startDate
- endDate
Mappings
The mappings are listed in the tables below.
Table 417: ChipSoft to SCIM user mapping
Ldap |
ldap |
Ldapdomain |
ldapDomain |
Gebruikersnaam |
id or userName |
Gebruikersomschrijving |
displayName |
Geblokkeerd |
active |
Startdate |
startDate |
Enddate |
endDate |
Afdeling |
department |
Functie |
position |
Soort |
kind |
Uzinr |
uzinNo |
Rolecode |
roles { value = RoleCode display = RoleCode type = blankValue } |
Bedrijf |
company |
Email |
emails { value = emailValue, primary = 'true, type = 'work' } |
Laatsteinlogdatum |
lastLoginDate |
Laatsteinlogtijdstip |
lastLoginTime |
Login Groups |
Inloggroepcode |
value |
Inloggroepzoekcode |
searchCode |
User Group |
Groepcode |
value |
Zoekcode |
searchCode |
Table 418: ChipSoft to SCIM user group mapping
groepcode |
id |
zoekcode |
searchCode |
groepomschrijving |
displayName |
soortcode |
typeCode |
soortomschrijving |
speciesDescription |
Table 419: ChipSoft to SCIM login group mapping
inloggroepcode |
id |
inloggroepzoekcode |
searchCode |
inloggroepomschrijving |
displayName |
inloggroepactief |
active |
Connector limitations
Due to target behavior, following has been observed:
-
User Groups and Login Groups result don’t support pagination.
-
Memberships are not managed under Groups. Instead Groups are managed under Users.
-
For any junk value in cursor, it fetches records from target. It returns last login date as "0001-01-01T00:00:00Z" and time "12:00:00" for some of the records.
-
Email is not available for any user, target also does not accept new user with email.
-
Delete is not available for any user.
-
Some of the fields are not created during create user request.
-
System throws an error when it is trying to create an existing user. It displays the value of “ldap“ in error description instead of “userName“.
-
userName (Gebruikersnaam) fields only accept 8 characters. Any string more than 8 characters will be truncated and only first 8 characters are saved.