DataDog
DataDog is a monitoring service for cloud-scale applications. It provides monitoring services for monitoring servers, databases, tools, and services, using a SaaS-based data analytics platform.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 82: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User by id |
GET |
Get All Users |
GET |
Mandatory field
Users
User mapping
The user mappings are listed in the tables below.
Table 83: User mapping
Id |
handle |
UserName |
email |
Name.Formatted |
name |
DisplayName |
name |
Emails[].Value |
email |
Roles[].Value |
access_role |
Roles[].Display |
roles[].name |
Active |
disabled |
Connector limitations
-
The email ID of users cannot be updated.
-
You cannot create duplicate users. When you try to create a duplicate user, you do not get any warning message.
-
The list of roles for the connector require timely update according to the changes at the target system.
-
The creation of an user with administration access role requires administrators application key.
-
Users are created with DataDog Standard role by default if it is not specified in the request.
- Test Connectivity may display 502 Bad Gateway error inconsistently, due to cloud application behavior.
Hideez
Hideez Group is a US based office development company that manufactures wireless multifunctional security key class electronic devices.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
-
Username
- Password
-
Target URL
Supported objects and operations
AccessProfile
Table 84: Supported operations for AccessProfile
Create AccessProfile |
POST |
Update AccessProfile |
PUT |
Delete AccessProfile |
DELETE |
Get AccessProfile |
GET |
Get All AccessProfiles |
GET |
Companies
Table 85: Supported operations for Companies
Create Company |
POST |
Update Company |
PUT |
Delete Company |
DELETE |
Get Company |
GET |
Get All Companies |
GET |
Departments
Table 86: Supported operations for Departments
Create Department |
POST |
Update Department |
PUT |
Delete Department |
DELETE |
Get Department |
GET |
Get All Departments |
GET |
Devices
Table 87: Supported operations for Devices
Update Devices |
PUT |
Get Devices |
GET |
Get All Devices |
GET |
Positions
Table 88: Supported operations for Positions
Create Positions |
POST |
Update Positions |
PUT |
Delete Positions |
DELETE |
Get Positions |
GET |
Get All Positions |
GET |
Workstations
Table 89: Supported operations for Workstations
Update Workstation |
PUT |
Get Workstation |
GET |
Get All Workstations |
GET |
Employees
Table 90: Supported operations for Employees
Create Employee |
POST |
Update Employee |
PUT |
Delete Employee |
DELETE |
Get Employee |
GET |
Get All Employees |
GET |
Mandatory fields
This section lists the mandatory fields required to create a resource type.
AccessProfiles
Table 91: Mandatory feilds for AccessProfiles
Name |
Yes |
Yes |
PinLength |
Yes |
Yes |
PinTryCount |
Yes |
Yes |
PinExpiration |
Yes |
Yes |
buttonBonding |
No |
Yes |
buttonConnection |
No |
Yes |
buttonNewChannel |
No |
Yes |
pinNewChannel |
No |
Yes |
masterKeyConnection |
No |
Yes |
masterKeyNewChannel |
No |
Yes |
Companies
Departments
Devices (Update)
Positions
Workstations (Update)
Employees
- FirstName
- LastName
- Email
- DepartmentId
- PositionId
Mappings
The mappings are listed in the tables below.
Table 92: Employee mapping
Id |
id |
UserName |
UserName |
firstName |
firstName |
lastName |
lastName |
email |
email |
phoneNumber |
phoneNumber |
departmentId |
departmentId |
positionId |
positionId |
device.id |
device.id |
device.mac |
device.mac |
device.model |
device.model |
device.rfid |
device.rfid |
device.mac |
device.mac |
device.model |
device.model |
device.rfid |
device.rfid |
device.batterydevice.battery |
device.batterydevice.battery |
device.firmware |
deviceirmware |
device.state |
device.state |
device.lastSynced |
device.lastSynced |
device.employeeId |
device.employeeId |
device.primaryAccountId |
device.primaryAccountId |
device.acceessProfileId |
device.acceessProfileId |
device.masterPassword |
device.masterPassword |
device.importedAt |
device.importedAt |
device.isOnline |
device.isOnline |
device.deviceAccessProfile.Id |
device.deviceAccessProfile.Id |
device.deviceAccessProfile. name |
device.deviceAccessProfile. name |
device.deviceAccessProfile.createdAt |
device.deviceAccessProfile. createdAt |
device.deviceAccessProfile. updatedAt |
device.deviceAccessProfile. updatedAt |
device.deviceAccessProfile. buttonBonding |
device.deviceAccessProfile. buttonBonding |
device.deviceAccessProfile. buttonConnection |
device.deviceAccessProfile. buttonConnection |
device.deviceAccessProfile. buttonNewChannel |
device.deviceAccessProfile. buttonNewChannel |
device.deviceAccessProfile. pinBonding |
device.deviceAccessProfile. pinBonding |
device.deviceAccessProfile.pinConnection |
device.deviceAccessProfile.buttonConnection |
device.deviceAccessProfile.pinNewChannel |
device.deviceAccessProfile.buttonNewChannel |
device.deviceAccessProfile.masterKeyBonding |
device.deviceAccessProfile.pinBonding |
device.deviceAccessProfile.masterKeyConnection |
device.deviceAccessProfile.pinConnection |
device.deviceAccessProfile.masterKeyNewChannel |
device.deviceAccessProfile.pinNewChannel |
device.deviceAccessProfile.pinExpiration |
device.deviceAccessProfile.pinExpiration |
device.deviceAccessProfile.pinLength |
device.deviceAccessProfile.pinLength |
device.deviceAccessProfile.pinTryCount |
device.deviceAccessProfile.pinTryCount |
device.deviceAccessProfile.pinExpirationConverted |
device.deviceAccessProfile.pinExpirationConverted |
device.deviceAccessProfile.pinExpirationString |
device.deviceAccessProfile.pinExpirationString |
department.Id |
department.Id |
department.companyId |
department.companyId |
department.name |
department.name |
department.company.id |
department.company.id |
department.company.name |
department.company.name |
position.id |
position.id |
position.name |
position.name |
fullName |
fullName |
empCompany |
empCompany |
empDepartment |
empDepartment |
currentDevice |
currentDevice |
Table 93: AccessProfile mapping
Id |
Id |
name |
name |
createdAt |
createdAt |
updatedAt |
updatedAt |
buttonBonding |
buttonBonding |
buttonConnection |
buttonConnection |
buttonNewChannel |
buttonNewChannel |
pinBonding |
pinBonding |
pinConnection |
pinConnection |
pinNewChannel |
pinNewChannel |
masterKeyBonding |
masterKeyBonding |
masterKeyConnection |
masterKeyConnection |
masterKeyNewChannel |
masterKeyNewChannel |
pinExpiration |
pinExpiration |
pinLength |
pinLength |
pinTryCount |
pinTryCount |
pinExpirationConverted |
pinExpirationConverted |
pinExpirationString |
pinExpirationString |
device.id |
device.id |
device.mac |
device.mac |
device.model |
device.model |
device.rfid |
device.rfid |
device.battery |
device.battery |
device.firmware |
device.firmware |
device.battery |
device.battery |
device.state |
device.state |
device.lastSynced |
device.lastSynced |
device.employeeId |
device.employeeId |
device.primaryAccountId |
device.primaryAccountId |
device.acceessProfileId |
device.acceessProfileId |
device.masterPassword |
device.masterPassword |
device.importedAt |
device.importedAt |
device.isOnline |
device.isOnline |
Table 94: Company mapping
id |
id |
name |
name |
Table 95: Department mapping
Id |
Id |
companyId |
companyId |
name |
name |
company.id |
company.id |
company.name |
company.name |
Table 96: Device mapping
Id |
Id |
mac |
mac |
model |
model |
rfid |
rfid |
battery |
battery |
firmware |
firmware |
state |
state |
lastSynced |
lastSynced |
employeeId |
employeeId |
primaryAccountId |
primaryAccountId |
acceessProfileId |
acceessProfileId |
masterPassword |
masterPassword |
importedAt |
importedAt |
isOnline |
isOnline |
deviceAccessProfile.Id |
deviceAccessProfile.Id |
deviceAccessProfile.name |
deviceAccessProfile.name |
deviceAccessProfile.createdAt |
deviceAccessProfile.createdAt |
deviceAccessProfile.updatedAt |
deviceAccessProfile.updatedAt |
deviceAccessProfile.buttonBonding |
deviceAccessProfile.buttonBonding |
deviceAccessProfile.buttonConnection |
deviceAccessProfile.buttonConnection |
deviceAccessProfile.buttonNewChannel |
deviceAccessProfile.buttonNewChannel |
deviceAccessProfile.pinBonding |
deviceAccessProfile.pinBonding |
deviceAccessProfile.pinConnection |
deviceAccessProfile.pinConnection |
deviceAccessProfile.pinNewChannel |
deviceAccessProfile.pinNewChannel |
deviceAccessProfile.masterKeyBonding |
deviceAccessProfile.masterKeyBonding |
deviceAccessProfile.masterKeyConnection |
deviceAccessProfile.masterKeyConnection |
deviceAccessProfile.masterKeyNewChannel |
deviceAccessProfile.masterKeyNewChannel |
deviceAccessProfile.pinExpiration |
deviceAccessProfile.pinExpiration |
deviceAccessProfile.pinLength |
deviceAccessProfile.pinLength |
deviceAccessProfile.pinTryCount |
deviceAccessProfile.pinTryCount |
deviceAccessProfile.pinExpirationConverted |
deviceAccessProfile.pinExpirationConverted |
deviceAccessProfile.pinExpirationString |
deviceAccessProfile.pinExpirationString |
Table 97: Position mapping
id |
id |
name |
name |
Table 98: Workstation mapping
Id |
Id |
name |
name |
domain |
domain |
clientVersion |
clientVersion |
departmentId |
departmentId |
departmentName |
departmentName |
os |
os |
ip |
ip |
lastSeen |
lastSeen |
approved |
approved |
rfid |
rfid |
companyId |
companyId |
companyName |
department.company.name |
proximityDevices[].Id |
proximityDevices[].Id |
proximityDevices[].deviceId |
proximityDevices[].deviceId |
proximityDevices[].workstationId |
proximityDevices[].workstationId |
proximityDevices[].lockProximity |
proximityDevices[].lockProximity |
proximityDevices[].unlockProximity |
proximityDevices[].unlockProximity |
proximityDevices[].lockTimeout |
proximityDevices[].lockTimeout |
Connector limitations
You cannot edit an unapproved workstation. You can only edit approved workstations.
One Identity Manager E2E integration needs
For more information, see One Identity Manager E2E integration needs for Hideez connector.
Opsgenie
Opsgenie is a modern incident management platform for operating always-on services, empowering Dev & Ops teams to plan for service disruptions and stay in control during incidents. With over 200 deep integrations and a highly flexible rules engine, Opsgenie centralizes alerts, notifies the right people reliably, and enables them to collaborate and take rapid action. Throughout the entire incident lifecycle, Opsgenie tracks all activity and provides actionable insights to improve productivity and drive continuous operational efficiencies.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 99: Supported operations for Users
Create User |
POST |
Get User |
GET |
Get Users |
GET |
Update User |
PUT |
Delete User |
DELETE |
Groups
Table 100: Supported operations for Groups
Create Group |
POST |
Get Group |
GET |
Get Groups |
GET |
Update Group |
PUT |
Delete Group |
DELETE |
Roles
Table 101: Supported operations for Roles
Get custom user role |
GET |
Get custom user roles |
GET |
Mandatory fields
This section lists the mandatory fields required to create a User or Group.
Users
-
emails[].value
-
displayName
Groups
Mappings
The mappings are listed in the tables below.
Users
Table 102: User mapping
id |
id |
username |
userName |
fullName |
name.formatted |
fullName |
displayName |
username |
emails[0].value |
userAddress.line |
addresses[].streetAddress |
userAddress.city |
addresses[].locality |
userAddress.state |
addresses[].region |
userAddress.zipCode |
addresses[].postalCode |
userAddress.country |
addresses[].country |
blocked |
active |
locale |
locale |
timeZone |
timezone |
role.id |
roles[].value |
user teams[].id |
groups[].value |
skypeUsername |
userExtension.skypeUsername |
createdAt |
meta.created |
Groups
Table 103: Group mapping
id |
id |
name |
displayName |
members[]user.id |
members[].value |
description |
extension.description |
createdAt |
meta.created |
Connector limitations
- When you update an user, the updated emailID will not be retrieved until it is verified by the user.
- When you create or update a Group, you can use only dots, dashes and underscores for Group names.
Informatica Cloud Services
Informatica Cloud Services
Informatica Cloud Services deliver purpose-built data integration cloud applications that allow business users to integrate data across cloud-based applications and on-premise systems and databases. Informatica Cloud Services address specific business processes and point-to-point data integration.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 104: Supported operations for Users
Create User |
POST |
Get User |
GET |
Get all Users |
GET |
Delete User |
DELETE |
Groups
Table 105: Supported operations for Groups
Create Group |
POST |
Get Group |
GET |
Get all Groups |
GET |
Delete Group |
DELETE |
Roles
Table 106: Supported operations for Roles
Get all roles |
GET |
Get role |
GET |
Mandatory fields
This section lists the mandatory fields required to create a User or Group:
Users
-
userName
-
name.givenName
-
name.familyName
-
emails[].value
-
entitlements[].value
NOTE: The first available entitlement from the target system would be assigned to entitlements[].value if the property is not provided in the SCIM request. The entitlement property is Roles from the target system.
Groups
- displayName
- entitlements[].value
NOTE: The first available entitlement from the target system would be assigned to entitlements[].value if the property is not provided in the SCIM request. The entitlement property is Roles from the target system.
Mappings
The user and group mappings are listed in the tables below.
Table 107: User mapping
id |
id |
userName |
userName |
lastName |
name.familyName |
firstName lastName |
name.formatted |
firstName lastName |
displayName |
email |
emails[0].value |
title |
title |
state |
active |
locale |
locale |
timeZoneId |
timezone |
roles[].id |
roles[].value |
roles[].roleName |
roles[].display |
groups[].id |
groups[].value |
groups[].userGroupName |
groups[].display |
orgId |
userExtension.orgId |
description |
userExtension.description |
authentication |
userExtension.authentication |
forcePasswordChange |
userExtension.forcePasswordChange |
maxLoginAttempts |
userExtension.maxLoginAttempts |
createTime |
meta.created |
updateTime |
meta.lastModified |
Groups
Table 108: Group mapping
id |
id |
userGroupName |
displayName |
users[].id |
members[].value |
users[].userName |
members[].display |
roles[].id |
roles[].value |
roles[].roleName |
roles[].display |
orgId |
userExtension.orgId |
description |
extension.description |
createTime |
meta.created |
updateTime |
meta.lastModified |
Roles
Table 109: Roles mapping
id |
id |
name |
roleName |
Connector limitations
-
The connector does not support update operation for users and groups as the target cloud system does not support update operation for users and groups.
- Target system roles are mapped against the entitlements in SCIM connector.
-
While creating a user or a group, role ids (entitlements) are required. It is not possible to assign entitlements from One Identity Manager client during the creation of users or groups. Hence, a logic has been added in the Starling Connect to retrieve all the roles from the target system and assign the first role (except for those which contain admin in role name) to the create resource request.