The Apigee connector allows you to connect Apigee with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Apigee's platform that allows you to design, secure, analyze, scale, publish, monitor, and manage the APIs.

To configure the connector, following parameters are required:

• Connector name

• UserName

• Password

• Organization

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

Supported objects and operations

Users

Table 316: Supported operations for Users

Operation	VERB
Create User	POST
Update User	PUT
Delete User	DELETE
Get User by ID	GET
Get All Users	GET

Roles

Table 317: Supported operations for Roles

Operation	Operation
Get Role by id	GET
Get All Roles	GET

Mandatory fields

This section lists the mandatory fields required to create a User or Group:

Users

• Name.GivenName

• Name.FamilyName

• Emails.Value

• Password

User and Group mapping

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

Table 318: User mapping

SCIM Parameter	Apigee parameter
id	emailId
userName	emailId
DisplayName	firstName+lastName
Name.GivenName	firstName
Name.FamilyName	lastName
Emails.Value	emailId
Roles[].value	(userRolesResponse)role[].name
Password	Password

Role

Table 319: Role mapping

SCIM Parameter	Apigee parameter
id	name
name	name

Connector limitations

• At least one role must be assigned to the created user. If the role is not assigned to the user, the particular user is not visible on the User management dashboard of the target instance due to the limitation of the target system.

• Get All Users does not return the displayName as it is not available in the target system. However, Get User by ID returns the display name with the other available attributes of the User.

• Create User operation fails intermittently and an Internal Server Error 500 is displayed due to the Target system API behavior.

• The Get All and Create User operations may occasionally take more time to respond for requests.

• Apigee Connector does not support pagination for Users and Roles object types due to API limitation in the target system.
• 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.

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.