지금 지원 담당자와 채팅
지원 담당자와 채팅

Starling Connect Hosted - One Identity Manager Administration Guide

About this guide One Identity Starling Connect overview One Identity Starling Supported cloud applications Working with connectors Connector versions Salesforce Facebook Workplace SAP Cloud Platform JIRA Server RSA Archer SuccessFactors Amazon S3 AWS ServiceNow Dropbox Crowd Atlassian JIRA Confluence Trello Box Pipedrive SuccessFactors HR NutShell Insightly Egnyte SugarCRM Oracle IDCS Statuspage Zendesk Sell Workbooks DocuSign Citrix ShareFile Zendesk Azure AD Google Workspace Concur Tableau GoToMeeting Coupa AWS Cognito Okta DataDog Hideez Opsgenie Informatica Cloud Services AppDynamics Marketo Workday HR OneLogin PingOne Aha! SAP Litmos HackerRank Slack ActiveCampaign Webex Apigee Databricks Hive PagerDuty Dayforce Smartsheet Pingboard SAP Cloud for Customer Azure Infrastructure Oracle Fusion Cloud Majesco LuccaHR OpenText Appendix: Creating a service account in Google Workspace Appendix: Setting a trial account on Salesforce Registering the application, providing necessary permissions, retrieving Client Id and Client Secret from the Azure AD tenant Generating a private key for service account in GoToMeeting Configuring Amazon S3 AWS connector to support entitlements for User and Group Configuring Box connector to support additional email IDs for users One Identity Manager E2E integration needs for Hideez connector Configuring custom attributes for ServiceNow v.1.0 Configuring custom attributes for Coupa v.1.0 Configuring custom attributes in connectors Disabling attributes Configuring a connector that uses the consent feature Synchronization and integration of Roles object type with One Identity Manager Synchronization and integration of Workspaces object type with One Identity Manager Synchronization and integration of Products object type with One Identity Manager User centric membership Creating multi-valued custom fields in One Identity Manager Synchronization and assignment of PermissionSets to Users with One Identity Manager Connectors that support password attribute in User object Connectors that do not support special characters in the object ID Creating an app for using SCIM on Slack Enterprise Grid Organization Creating a Webex integration application, providing necessary scopes, retrieving Client Id and Client Secret Retrieving the API key from Facebook Workplace Outbound IP addresses Values for customer-specific configuration parameters in Workday HR connector Initiate an OAuth connection to SuccessFactors Creating custom editable/upsertable attributes in Successfactors employee central Custom Foundation Objects in Successfactors HR connector Configuring additional datetime offset in connectors How to Create custom attribute for Users in SuccessFactors portal SAP Cloud for Customer - Steps to add custom fields at One Identity Manager attributes Creating Service Principal to authenticate the Azure resource management REST APIs for Azure Infrastructure connector

Supported objects and operations

LuccaHR provides solutions to optimize administrative and HR processes.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API Key

  • Target URL (https://{instance}.ilucca-demo.net/)

Users

Table 366: Supported operations for Users

Operation

VERB

Create User

POST

Get a user

GET

List Users

GET

Update a user

PUT

Departments

Table 367: Supported operations for Departments

Operation

VERB

Create a department

POST

Delete a department

DELETE

Get a department

GET

List department

GET

Update a department

PUT

Mandatory fields

Users

  • name.firstName

  • name.lastName

  • userName

  • email.value

  • extension.legalEntityId

  • extension. departmentId

Departments

  • name

User and Department mapping

The user and department mappings are listed in the tables below.

Table 368: User mapping
SCIM parameter LuccaHR parameter
displayName displayName
Emails.Value mail

Extension.birthDate

birthDate

Extension.contractEnd

dtContractEnd

Extension.contractStart

dtContractStart

Extension.department.name

department.name

Extension.department.value

departmentID

Extension.employeeNumber

employeeNumber

Extension.gender

gender

Extension.legalEntity.name

legalEntity.name

Extension.legalEntity.value

legalEntityID

Extension.manager.name

manager.name

Extension.Manager.Value

managerID

Extension.rolePrincipal.name

rolePrincipal.name

Extension.rolePrincipal.value

rolePrincipalId

Id id

meta.Created

createdOn

meta.LastModified

modifiedOn

Name.FamilyName lastName

Name.Formatted

name

Name.GivenName firstName

Roles[].display

habilitedRoles[].name

Roles[].value

habilitedRoles[].id

Title

jobTitle

UserName login
Table 369: Department mapping
SCIM parameter LuccaHR parameter
id id
name name
code code
Active isActive
head.value headID
head.name head.name
members[].value users[].id

members[].display

users[].name

meta.Created

createdOn

meta.LastModified

modifiedOn

Connector limitations

  • A user once created cannot be deleted, but it can be terminated using the PUT API.

  • Multiple departments with same name can be created.

  • Departments with one or more active users cannot be deleted.

Mandatory fields

LuccaHR provides solutions to optimize administrative and HR processes.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API Key

  • Target URL (https://{instance}.ilucca-demo.net/)

Supported objects and operations

Users

Table 366: Supported operations for Users

Operation

VERB

Create User

POST

Get a user

GET

List Users

GET

Update a user

PUT

Departments

Table 367: Supported operations for Departments

Operation

VERB

Create a department

POST

Delete a department

DELETE

Get a department

GET

List department

GET

Update a department

PUT

Users

  • name.firstName

  • name.lastName

  • userName

  • email.value

  • extension.legalEntityId

  • extension. departmentId

Departments

  • name

User and Department mapping

The user and department mappings are listed in the tables below.

Table 368: User mapping
SCIM parameter LuccaHR parameter
displayName displayName
Emails.Value mail

Extension.birthDate

birthDate

Extension.contractEnd

dtContractEnd

Extension.contractStart

dtContractStart

Extension.department.name

department.name

Extension.department.value

departmentID

Extension.employeeNumber

employeeNumber

Extension.gender

gender

Extension.legalEntity.name

legalEntity.name

Extension.legalEntity.value

legalEntityID

Extension.manager.name

manager.name

Extension.Manager.Value

managerID

Extension.rolePrincipal.name

rolePrincipal.name

Extension.rolePrincipal.value

rolePrincipalId

Id id

meta.Created

createdOn

meta.LastModified

modifiedOn

Name.FamilyName lastName

Name.Formatted

name

Name.GivenName firstName

Roles[].display

habilitedRoles[].name

Roles[].value

habilitedRoles[].id

Title

jobTitle

UserName login
Table 369: Department mapping
SCIM parameter LuccaHR parameter
id id
name name
code code
Active isActive
head.value headID
head.name head.name
members[].value users[].id

members[].display

users[].name

meta.Created

createdOn

meta.LastModified

modifiedOn

Connector limitations

  • A user once created cannot be deleted, but it can be terminated using the PUT API.

  • Multiple departments with same name can be created.

  • Departments with one or more active users cannot be deleted.

User and Department mapping

LuccaHR provides solutions to optimize administrative and HR processes.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API Key

  • Target URL (https://{instance}.ilucca-demo.net/)

Supported objects and operations

Users

Table 366: Supported operations for Users

Operation

VERB

Create User

POST

Get a user

GET

List Users

GET

Update a user

PUT

Departments

Table 367: Supported operations for Departments

Operation

VERB

Create a department

POST

Delete a department

DELETE

Get a department

GET

List department

GET

Update a department

PUT

Mandatory fields

Users

  • name.firstName

  • name.lastName

  • userName

  • email.value

  • extension.legalEntityId

  • extension. departmentId

Departments

  • name

The user and department mappings are listed in the tables below.

Table 368: User mapping
SCIM parameter LuccaHR parameter
displayName displayName
Emails.Value mail

Extension.birthDate

birthDate

Extension.contractEnd

dtContractEnd

Extension.contractStart

dtContractStart

Extension.department.name

department.name

Extension.department.value

departmentID

Extension.employeeNumber

employeeNumber

Extension.gender

gender

Extension.legalEntity.name

legalEntity.name

Extension.legalEntity.value

legalEntityID

Extension.manager.name

manager.name

Extension.Manager.Value

managerID

Extension.rolePrincipal.name

rolePrincipal.name

Extension.rolePrincipal.value

rolePrincipalId

Id id

meta.Created

createdOn

meta.LastModified

modifiedOn

Name.FamilyName lastName

Name.Formatted

name

Name.GivenName firstName

Roles[].display

habilitedRoles[].name

Roles[].value

habilitedRoles[].id

Title

jobTitle

UserName login
Table 369: Department mapping
SCIM parameter LuccaHR parameter
id id
name name
code code
Active isActive
head.value headID
head.name head.name
members[].value users[].id

members[].display

users[].name

meta.Created

createdOn

meta.LastModified

modifiedOn

Connector limitations

  • A user once created cannot be deleted, but it can be terminated using the PUT API.

  • Multiple departments with same name can be created.

  • Departments with one or more active users cannot be deleted.

Connector limitations

LuccaHR provides solutions to optimize administrative and HR processes.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API Key

  • Target URL (https://{instance}.ilucca-demo.net/)

Supported objects and operations

Users

Table 366: Supported operations for Users

Operation

VERB

Create User

POST

Get a user

GET

List Users

GET

Update a user

PUT

Departments

Table 367: Supported operations for Departments

Operation

VERB

Create a department

POST

Delete a department

DELETE

Get a department

GET

List department

GET

Update a department

PUT

Mandatory fields

Users

  • name.firstName

  • name.lastName

  • userName

  • email.value

  • extension.legalEntityId

  • extension. departmentId

Departments

  • name

User and Department mapping

The user and department mappings are listed in the tables below.

Table 368: User mapping
SCIM parameter LuccaHR parameter
displayName displayName
Emails.Value mail

Extension.birthDate

birthDate

Extension.contractEnd

dtContractEnd

Extension.contractStart

dtContractStart

Extension.department.name

department.name

Extension.department.value

departmentID

Extension.employeeNumber

employeeNumber

Extension.gender

gender

Extension.legalEntity.name

legalEntity.name

Extension.legalEntity.value

legalEntityID

Extension.manager.name

manager.name

Extension.Manager.Value

managerID

Extension.rolePrincipal.name

rolePrincipal.name

Extension.rolePrincipal.value

rolePrincipalId

Id id

meta.Created

createdOn

meta.LastModified

modifiedOn

Name.FamilyName lastName

Name.Formatted

name

Name.GivenName firstName

Roles[].display

habilitedRoles[].name

Roles[].value

habilitedRoles[].id

Title

jobTitle

UserName login
Table 369: Department mapping
SCIM parameter LuccaHR parameter
id id
name name
code code
Active isActive
head.value headID
head.name head.name
members[].value users[].id

members[].display

users[].name

meta.Created

createdOn

meta.LastModified

modifiedOn

  • A user once created cannot be deleted, but it can be terminated using the PUT API.

  • Multiple departments with same name can be created.

  • Departments with one or more active users cannot be deleted.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택