Connector limitations
SAP Cloud Platform is an open Platform as a Service (PaaS) that offers users in-memory capabilities, core platform services, and business services for cloud applications.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 19: Supported operations for Users
Create |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get |
GET |
Pagination |
GET |
Groups
Table 20: Supported operations for Groups
Create |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 21: User mapping
Id |
id |
UserName |
userName |
Name.GivenName |
givenName |
Name.FamilyName |
familyName |
Name.HonorificPrefix |
name.honorificPrefix |
DisplayName |
displayName |
Emails.Value |
email.value |
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 |
UserType |
userType |
Locale |
locale |
Timezone |
timeZone |
Active |
active |
Groups.value |
group.$ref |
Groups.display |
group.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.ContactPreferenceTelephone |
contactPreferenceTelephone |
Extension.IndustryCrm |
industryCrm |
Extension.PasswordStatus |
passwordStatus |
Extension.MailVerified |
mailVerified |
Extension.CompanyRelationship |
companyRelationship |
Extension.ContactPreferenceEmail |
contactPreferenceEmail |
Extension.SourceSystem |
sourceSystem |
Extension.CostCenter |
extension.costCenter |
Extension.EmployeeNumber |
extension.employeeNumber |
Extension.CorporateGroups |
corporateGroups.value |
Extension.customAttributes.name |
attributes.name |
Extension.customAttributes.value |
attributes.value |
Meta.Created |
meta.created |
Meta.LastModified |
meta.lastModified |
Table 22: Group mapping
id |
name |
DisplayName |
displayName |
Members.value |
members.value |
Members.display |
members.display |
Extension.GroupName |
extension.name |
Extension.Description |
extension.description |
-
A performance impact is expected, with a list response of Groups because each record is retrieved and counted, since SCP Groups APIs do not provide totalResults.
-
ServiceProviderAuthority contains only Id field with the same value as the tenant id of the SCP instance, as there are no APIs that can fetch the tenant details in SCP.
-
Get All Groups and Get particular group with ID operations do not retrieve Created and Last Modified fields for Groups object types.
JIRA Server
JIRA Server is an issue-tracking product used for project management, generating project reports, and bug tracking.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
-
Username
- Password
-
SCIM URL
Supported objects and operations
Users
Table 23: Supported operations for Users
Remove/Provision |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get All Users |
GET |
Pagination |
GET |
Groups
Table 24: Supported operations for Groups
Create |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get All Groups |
GET |
Get Groups (Id) |
GET |
Roles
Table 25: Supported operations for Roles
Get All Roles |
GET |
Get Role (Id) |
GET |
Mandatory fields
Users
- User name
- Display name
- Email ID
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 26: User mapping
Id |
name |
UserName |
name |
password |
password |
Name.Formatted |
displayName |
DisplayName |
displayName |
Emails.Value |
emailAddress |
Locale |
locale |
Timezone |
timeZone |
Active |
active |
Groups.value |
group.name |
Groups.display |
group.name |
Table 27: Group mapping
Id |
name |
DisplayName |
name |
Members.value |
user.name |
Members.display |
user.displayName |
Connector limitations
- The following dates are not available in User and Group resources.
-
Pagination is not supported for Groups.
-
Update Group can only be used for membership management.
-
Since the application does not support id, the URL encoded user name or group name is assigned as id for the resource.
-
Leading slash (/) in clientRequest, in the RequestWrapper is restricted in REST Client (Eg: Postman) testing.
-
Invalid host name in target URL returns error 500.
- The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID
Supervisor configuration parameters
JIRA Server is an issue-tracking product used for project management, generating project reports, and bug tracking.
To configure the connector, following parameters are required:
-
Connector name
-
Username
- Password
-
SCIM URL
Supported objects and operations
Users
Table 23: Supported operations for Users
Remove/Provision |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get All Users |
GET |
Pagination |
GET |
Groups
Table 24: Supported operations for Groups
Create |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get All Groups |
GET |
Get Groups (Id) |
GET |
Roles
Table 25: Supported operations for Roles
Get All Roles |
GET |
Get Role (Id) |
GET |
Mandatory fields
Users
- User name
- Display name
- Email ID
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 26: User mapping
Id |
name |
UserName |
name |
password |
password |
Name.Formatted |
displayName |
DisplayName |
displayName |
Emails.Value |
emailAddress |
Locale |
locale |
Timezone |
timeZone |
Active |
active |
Groups.value |
group.name |
Groups.display |
group.name |
Table 27: Group mapping
Id |
name |
DisplayName |
name |
Members.value |
user.name |
Members.display |
user.displayName |
Connector limitations
- The following dates are not available in User and Group resources.
-
Pagination is not supported for Groups.
-
Update Group can only be used for membership management.
-
Since the application does not support id, the URL encoded user name or group name is assigned as id for the resource.
-
Leading slash (/) in clientRequest, in the RequestWrapper is restricted in REST Client (Eg: Postman) testing.
-
Invalid host name in target URL returns error 500.
- The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID
Supported objects and operations
JIRA Server is an issue-tracking product used for project management, generating project reports, and bug tracking.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
-
Username
- Password
-
SCIM URL
Users
Table 23: Supported operations for Users
Remove/Provision |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get All Users |
GET |
Pagination |
GET |
Groups
Table 24: Supported operations for Groups
Create |
POST |
Update (Id) |
PUT |
Delete (Id) |
DELETE |
Get (Id) |
GET |
Get All Groups |
GET |
Get Groups (Id) |
GET |
Roles
Table 25: Supported operations for Roles
Get All Roles |
GET |
Get Role (Id) |
GET |
Mandatory fields
Users
- User name
- Display name
- Email ID
Groups
User and Group mapping
The user and group mappings are listed in the tables below.
Table 26: User mapping
Id |
name |
UserName |
name |
password |
password |
Name.Formatted |
displayName |
DisplayName |
displayName |
Emails.Value |
emailAddress |
Locale |
locale |
Timezone |
timeZone |
Active |
active |
Groups.value |
group.name |
Groups.display |
group.name |
Table 27: Group mapping
Id |
name |
DisplayName |
name |
Members.value |
user.name |
Members.display |
user.displayName |
Connector limitations
- The following dates are not available in User and Group resources.
-
Pagination is not supported for Groups.
-
Update Group can only be used for membership management.
-
Since the application does not support id, the URL encoded user name or group name is assigned as id for the resource.
-
Leading slash (/) in clientRequest, in the RequestWrapper is restricted in REST Client (Eg: Postman) testing.
-
Invalid host name in target URL returns error 500.
- The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID