Opsgenie
The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
- API
-
Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)
-
Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details)
Supported objects and operations
Users
Table 229: Supported operations for Users
Create User |
POST |
Get User |
GET |
Get Users |
GET |
Update User |
PUT |
Delete User |
DELETE |
Groups
Table 230: Supported operations for Groups
Create Group |
POST |
Get Group |
GET |
Get Groups |
GET |
Update Group |
PUT |
Delete Group |
DELETE |
Roles
Table 231: 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 232: 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 233: 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.
Synchronization and integration of Roles object type with One Identity Manager
For more information, see Synchronization and integration of Roles object type with One Identity Manager
Supervisor configuration parameters
The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.
To configure the connector, following parameters are required:
-
Connector name
- API
-
Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)
-
Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details)
Supported objects and operations
Users
Table 229: Supported operations for Users
Create User |
POST |
Get User |
GET |
Get Users |
GET |
Update User |
PUT |
Delete User |
DELETE |
Groups
Table 230: Supported operations for Groups
Create Group |
POST |
Get Group |
GET |
Get Groups |
GET |
Update Group |
PUT |
Delete Group |
DELETE |
Roles
Table 231: 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 232: 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 233: 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.
Synchronization and integration of Roles object type with One Identity Manager
For more information, see Synchronization and integration of Roles object type with One Identity Manager
Supported objects and operations
The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
- API
-
Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)
-
Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details)
Users
Table 229: Supported operations for Users
Create User |
POST |
Get User |
GET |
Get Users |
GET |
Update User |
PUT |
Delete User |
DELETE |
Groups
Table 230: Supported operations for Groups
Create Group |
POST |
Get Group |
GET |
Get Groups |
GET |
Update Group |
PUT |
Delete Group |
DELETE |
Roles
Table 231: 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 232: 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 233: 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.
Synchronization and integration of Roles object type with One Identity Manager
For more information, see Synchronization and integration of Roles object type with One Identity Manager
Mandatory fields
The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
- API
-
Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)
-
Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details)
Supported objects and operations
Users
Table 229: Supported operations for Users
Create User |
POST |
Get User |
GET |
Get Users |
GET |
Update User |
PUT |
Delete User |
DELETE |
Groups
Table 230: Supported operations for Groups
Create Group |
POST |
Get Group |
GET |
Get Groups |
GET |
Update Group |
PUT |
Delete Group |
DELETE |
Roles
Table 231: Supported operations for Roles
Get custom user role |
GET |
Get custom user roles |
GET |
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 232: 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 233: 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.
Synchronization and integration of Roles object type with One Identity Manager
For more information, see Synchronization and integration of Roles object type with One Identity Manager