User and Group mapping
Oracle IDCS is a cloud-based identity management service that integrates with existing systems and directories. Users can develop, access and deploy their applications from one platform. It works with both cloud and on-premises applications.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 150: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get all users |
GET |
Get user by id |
GET |
Get users with Pagination |
GET |
Groups
Table 151: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get |
GET |
Get |
GET |
Mandatory fields
Users
-
userName
-
emails.value
-
name.familyName
Groups
The user and group mappings are listed in the tables below.
Table 152: User mapping
Id |
id |
userName |
userName |
externalId |
externalId |
name.givenName |
name.givenName |
name.familyName |
name.familyName |
name.middleName |
name.middleName |
name.formatted |
name.formatted |
name.honorificPrefix |
name.honorificPrefix |
name.honorificSuffix |
name.honorificSuffix |
displayName |
displayName |
nickName |
nickName |
emails.value |
email.value |
emails.type |
email.type |
emails.primary |
email.primary |
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 |
phoneNumbers.value |
phoneNumbers.value |
phoneNumbers.type |
phoneNumbers.type |
phoneNumbers.primary |
phoneNumbers.primary |
password |
password |
profileUrl |
profileUrl |
title |
title |
userType |
userType |
preferredLanguage |
preferredLanguage |
locale |
locale |
timezone |
timeZone |
active |
active |
entitlements.value |
entitlements.value |
entitlements.display |
entitlements.display |
entitlements.type |
entitlements.type |
roles.value |
roles.value |
roles.display |
roles.display |
roles.type |
roles.type |
groups.value |
groups.value |
groups.display |
groups.display |
extension.organization |
extension.organization |
extension.division |
extension.division |
extension.department |
extension.department |
extension.manager.value |
extension.manager.value |
extension.manager.displayName |
extension.manager.displayName |
extension.costCenter |
extension.costCenter |
extension.employeeNumber |
extension.employeeNumber |
meta.created |
meta.created |
meta.lastModified |
meta.lastModified |
Table 153: Group mapping
id |
id |
displayName |
displayName |
Members.value |
members.value |
Members.display |
members.display |
extension.externalId |
extension.externalId |
extension.description |
extension.description |
meta.created |
meta.created |
meta.lastModified |
meta.lastModified |
Connector limitations
-
Oracle IDCS does not validate the values provided for the roles in the user request and the same is getting assigned to the user. No validation is performed for the type, value properties for the roles. Same is the case with entitlements.
-
Groups will not be returned with the create user response.
-
Sub-Groups cannot be added in Group Memberships.
Connector limitations
Oracle IDCS is a cloud-based identity management service that integrates with existing systems and directories. Users can develop, access and deploy their applications from one platform. It works with both cloud and on-premises applications.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 150: Supported operations for Users
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get all users |
GET |
Get user by id |
GET |
Get users with Pagination |
GET |
Groups
Table 151: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get |
GET |
Get |
GET |
Mandatory fields
Users
-
userName
-
emails.value
-
name.familyName
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 152: User mapping
Id |
id |
userName |
userName |
externalId |
externalId |
name.givenName |
name.givenName |
name.familyName |
name.familyName |
name.middleName |
name.middleName |
name.formatted |
name.formatted |
name.honorificPrefix |
name.honorificPrefix |
name.honorificSuffix |
name.honorificSuffix |
displayName |
displayName |
nickName |
nickName |
emails.value |
email.value |
emails.type |
email.type |
emails.primary |
email.primary |
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 |
phoneNumbers.value |
phoneNumbers.value |
phoneNumbers.type |
phoneNumbers.type |
phoneNumbers.primary |
phoneNumbers.primary |
password |
password |
profileUrl |
profileUrl |
title |
title |
userType |
userType |
preferredLanguage |
preferredLanguage |
locale |
locale |
timezone |
timeZone |
active |
active |
entitlements.value |
entitlements.value |
entitlements.display |
entitlements.display |
entitlements.type |
entitlements.type |
roles.value |
roles.value |
roles.display |
roles.display |
roles.type |
roles.type |
groups.value |
groups.value |
groups.display |
groups.display |
extension.organization |
extension.organization |
extension.division |
extension.division |
extension.department |
extension.department |
extension.manager.value |
extension.manager.value |
extension.manager.displayName |
extension.manager.displayName |
extension.costCenter |
extension.costCenter |
extension.employeeNumber |
extension.employeeNumber |
meta.created |
meta.created |
meta.lastModified |
meta.lastModified |
Table 153: Group mapping
id |
id |
displayName |
displayName |
Members.value |
members.value |
Members.display |
members.display |
extension.externalId |
extension.externalId |
extension.description |
extension.description |
meta.created |
meta.created |
meta.lastModified |
meta.lastModified |
-
Oracle IDCS does not validate the values provided for the roles in the user request and the same is getting assigned to the user. No validation is performed for the type, value properties for the roles. Same is the case with entitlements.
-
Groups will not be returned with the create user response.
-
Sub-Groups cannot be added in Group Memberships.
Statuspage
Statuspage is a status and incident communication tool that helps service providers keep customers and employees informed during downtime. It lets users add separate components for each part of the infrastructure or functional part of service.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
-
API key (user API key under Manage Account → API tab) for the cloud account
-
Organization Id (Organization Id under Manage Account → API tab) for the cloud account
-
Target URL of the cloud account
-
Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details).
Supported objects and operations
Users
Table 154: Supported operations for Users
Create User |
POST |
Delete User |
DELETE |
Get User |
GET |
Get All Users |
GET |
Groups
Not Applicable
Mandatory fields
Users
Groups
Not Applicable
User and Group mapping
The user and group mappings are listed in the tables below.
Table 155: User mapping
Id |
id |
UserName |
email |
last_name |
name.familyName |
first_name |
name.givenName |
first_namelast_name |
name.formatted |
first_namelast_name |
displayName |
email |
emails[0].value |
created_at |
meta.created |
updated_at |
meta.lastModified |
Groups
Not Applicable
Connector limitations
-
Update operation for Users, resource type Groups and Pagination are not supported.
-
Retrieving a specific user would be relatively slow due to API limitations.
Supervisor configuration parameters
Statuspage is a status and incident communication tool that helps service providers keep customers and employees informed during downtime. It lets users add separate components for each part of the infrastructure or functional part of service.
To configure the connector, following parameters are required:
-
Connector name
-
API key (user API key under Manage Account → API tab) for the cloud account
-
Organization Id (Organization Id under Manage Account → API tab) for the cloud account
-
Target URL of the cloud account
-
Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details).
Supported objects and operations
Users
Table 154: Supported operations for Users
Create User |
POST |
Delete User |
DELETE |
Get User |
GET |
Get All Users |
GET |
Groups
Not Applicable
Mandatory fields
Users
Groups
Not Applicable
User and Group mapping
The user and group mappings are listed in the tables below.
Table 155: User mapping
Id |
id |
UserName |
email |
last_name |
name.familyName |
first_name |
name.givenName |
first_namelast_name |
name.formatted |
first_namelast_name |
displayName |
email |
emails[0].value |
created_at |
meta.created |
updated_at |
meta.lastModified |
Groups
Not Applicable
Connector limitations
-
Update operation for Users, resource type Groups and Pagination are not supported.
-
Retrieving a specific user would be relatively slow due to API limitations.