サポートと今すぐチャット
サポートとのチャット

Starling Connect Hosted - Active Roles Administration Guide

GoToMeeting

GoToMeeting is an online tool for meeting planning. The connector integrates with multiple other products and plug-ins, allowing users to easily connect to create, organize, and host meetings across a common platform.

For more information on generating a private key for a service account, see Generating a private key in GoToMeeting.

Supervisor Configuration Parameters

To configure the connector, following parameters are required:

  • Connector name

  • Username

  • Password
  • Client Id

  • Client Secret

  • Account key
  • Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.getgo.com/admin/rest/v1/)

Supported Objects and Operations

Users
Table 73: Supported operations for Users

Operation

VERB

Create User

POST

Update User

PUT

Delete User

DELETE

Deprovision

PUT

Undo Deprovision

PUT

Groups
Table 74: Supported operations for Groups

Operation

VERB

Create Group

POST

Update Group

PUT

Delete Group

DELETE

Mandatory Fields

Users
  • Email

  • givenName

  • familyName

Groups

displayName

Connector Limitations

  • For Users and Groups objects, the Created and Last Modified date are not displayed.

  • When trying to create a duplicate entry of the user who already exists, the connector returns status code 201.

  • Group membership operation is not supported.

  • When trying to retrieve a user by their ID using invalid alphanumeric IDs, the connector returns status code 502 instead of 404.
  • When trying to create a new user with the same email ID of a deleted user, the connector activates the deleted user instead of creating a new user.

 

Coupa

A Coupa connector allows users to move data in and out of Coupa. It lets you manage spend more efficiently by being able to integrate and access spend management and data for expenses, and integrate with other cloud applications.

Supervisor Configuration Parameters

To configure the connector, the following parameters are required:

  • Connector name

  • API key
  • Target URL (Cloud application's instance URL used as target URI in payload)

Supported Objects and Operations

Users
Table 75: Supported operations for Users

Operation

VERB

Create User

POST

Update User

PUT

Deprovision

PUT

Undo Deprovision

PUT

Mandatory Fields

Users
  • Username

  • Email
  • FirstName

  • LastName

Groups

NA

Connector Limitations

  • Total results are not supported due to cloud application limitations.

  • The target application supports soft delete of users. The deleted users are returned in GET and GET All. The users can also be deleted repeatedly.

  • Account-Groups will not work as of now. It will work when the Coupa team shares the source of information.

  • Approval-Groups will not work as of now. It will work when the new endpoint is implemented.

  • User-Groups will not work as of now. It will work when the new endpoint is implemented.

 

AWS Cognito

AWS Cognito is a connector from Amazon Web Services that helps developers build web and mobile apps that are more secure. It helps to better authenticate users. It also handles user data, including passwords, token-based authentication, scalability, permissions, and so on.

Supervisor Configuration Parameters

To configure the connector, following parameters are required:

  • Connector name

  • AccessKey Id

  • Access Secret

  • Region

  • User Pool Id

  • Target URL (Cloud application's instance URL used as target URI in payload)

Supported Objects and Operations

Users
Table 76: Supported operations for Users

Operation

VERB

Create User

POST

Update User

PUT

Delete User

DELETE

Groups
Table 77: Supported operations for Groups

Operation

VERB

Create Group

POST

Update Group

PUT

Delete Group

DELETE

Deprovision

PUT

Undo Deprovision

PUT

Update Membership

PUT

Mandatory Fields

Users
  • Username

  • Email
Groups

DisplayName

Connector Limitations

  • Creating or updating the User or a Group executes in multiple steps. Failure in any step is reported as a complete failure of operation. However, the record is persisted until succeeded steps.

  • Noncompliance to password policy returns an error. However, an User is created.

  • DesiredDeliveredMedium is write only property. By default, SMS is the default option and it is not returned in Get specific user response.

  • A User can be a member of a maximum of 25 groups.

Okta

Okta provides cloud software that helps companies manage and secure user authentication into modern applications, and for developers to build identity controls into applications, website web services and into devices.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Token

  • Target URL (Cloud application's instance URL used as targetURI in payload)

Supported objects and operations

Users
Table 78: Supported operations for Users

Operation

VERB

Create User POST
Update User PUT
Delete User DELETE
Groups
Table 79: Supported operations for Groups

Operation

VERB

Create Group POST
Update Group PUT
Delete Group DELETE
Create Membership POST

Add Membership

POST

Delete Membership

DELETE

Mandatory fields

Users
  • GivenName

  • FamilyName
  • Username
  • Email
  • Password
Groups
  • DisplayName

User and Group mapping

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

Table 80: User mapping
SCIM parameter Okta parameter
Id id
UserName login
DisplayName displayName
NickName nickName
Name.GivenName firstName
Name.FamilyName lastName
Name.MiddleName middleName
Name.HonorificPrefix honorificPrefix

Name.HonorificSuffix

honorificSuffix

Addresses.StreetAddress streetAddress
Addresses.Locality city
Addresses.Region state
Addresses.PostalCode zipCode
Addresses.Country countryCode
Emails.value email

PhoneNumbers.value

primaryPhone

UserType

userType

Title

title

PreferredLanguage

preferredLanguage

Locale

locale

Timezone

timezone

Groups[].value (On Demand)

Id (groupsForUserResponse)

Groups[].display (On Demand)

Profile.name (groupsForUserResponse)

Active

status == "ACTIVE"

Extension.EmployeeNumber

employeeNumber

Extension.Division

division

Extension.Department

department

Extension.CostCenter

costCenter

Extension.Organization

organization

Extension.Manager.value

managerId

Extension.Manager.DisplayName

manager

Meta.Created

created

Meta.LastModified

lastUpdated

Groups
Table 81: Group mapping
SCIM parameter Okta parameter
Id id
displayName profile.name
Extension.Description profile.description
Members[].value id (GetGroupMembersResponse[])
Members[].display profile.displayName (GetGroupMembersResponse[])
Meta.Created created
Meta.LastModified lastUpdated

Connector limitations

  • Get Users and Groups by pagination will return resources in multiples of 100. The resource count will be same as the next nearest multiple of 100. For example, if the count is specified as 325, the resource count will be 400.
  • Disabled User can be still be fetched.
  • Password update is not possible through the connector since it expects old and new passwords as parameter. Old password can never be fetched for any user.

  • UserName should be in the format of email id.

  • When you delete a user for the first time, the user will be deactivated. When you delete the user for the second time, the user will be deleted permanently from target system.

  • When you modify the email value, both the username and email values get updated. But when you modify the username alone, only the username gets updated with the username value.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択