User centric membership configuration for AppDynamics
The AppDynamics connector allows you to connect AppDynamics with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance the services provided by AppDynamics.
AppDynamics is a real-time business and application performance management and monitoring platform that provides a complete view of the application environment, allowing you to monitor and fix issues quickly.
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector name
-
Client Secret
-
API Client Name
-
Account Name
Supported objects and operations
Users
Table 240: Supported operations for Users
| Create User |
POST |
| Update User |
PUT |
| Delete User |
DELETE |
| Get User |
GET |
| Get All Users |
GET |
Groups
Table 241: Supported operations for Groups
| Create Group |
POST |
| Update Group |
PUT |
| Delete Group |
DELETE |
| Get Group |
GET |
| Get All Groups |
GET |
Roles
Table 242: Supported operations for Roles
| Get Role |
GET |
| Get All Roles |
GET |
Mandatory fields
This section lists the mandatory fields required to create a User or Group:
Users
-
UserName
-
DisplayName
-
Security_provider_type
- Password
Groups
- DisplayName
-
Security_provider_type
Mappings
The user, group, and roles mappings are listed in the tables below.
Table 243: User mapping
| Id |
id |
| UserName |
name |
| DisplayName |
displayName |
| password |
password |
| Groups[].value |
groups[].id |
| Groups[].display |
groups[].name |
| Roles[].value |
roles[].id |
| Roles[].display |
roles[].name |
| Extension.security_provider_type |
security_provider_type |
Groups
Table 244: Group mapping
| Id |
id |
| displayName |
name |
| Extension.Description |
description |
| Extension.security_provider_type |
security_provider_type |
| Extension.Roles[].value |
roles[].id |
| Extension.Roles[].display |
roles[].name |
Roles
Table 245: Roles mapping
| Id |
id |
| displayName |
name |
| description |
description |
Connector limitations
- Groups members information will not be retrieved in response to GET specific Group. The reason for this is the Groups API of the target system does not support it. However, the same is done at Users API. To overcome this deviation from standard behavior (rfc: https://tools.ietf.org/html/rfc7643#section-4.2), the connector is designed in such a way that all membership operations are done at Users endpoint. Hence, GET specific User response will retrieve the membership associations of respective User.
-
-
A performance impact is expected in the assignment operation of Roles and Group memberships when the User belongs to multiple Roles and Groups. The reason for this is that separate API calls are made for each and every Roles or Group membership association.
- AppDynamics target system returns the error code 500 for most of the error scenarios except for very specific errors such as 401 Unauthorized. However, the connector handles few of those generic errors and responds appropriately.
-
Most error messages returned by the target system are neither sufficiently informative nor available. The connector follows the same behavior, wherever custom error messages are not possible.
-
Due to target system limitations, password update of User is not supported by the connector. However, the password can be set at the time of creation.
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
For more information, see only the following sections in User centric membership:
Marketo
The Marketo connector allows you to connect Marketo with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance the services provided by Marketo.
Marketo provides marketing automation software for all types of digital marketing. It provides services to capture the interaction with each customer, enabling users to identify the most profitable channels and campaigns.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 246: Supported operations for Users
|
Create(Invite) User |
POST |
| Update User |
PUT |
| Delete User |
DELETE |
| Get User |
GET |
| Get All Users |
GET |
| Add RoleAndWorkspace to User |
PUT |
|
Remove RoleAndWorkspace from User |
PUT |
Roles
Table 247: Supported operations for Roles
| Get all Roles |
GET |
Workspaces
Table 248: Supported operations for Workspaces
| Get all Workspaces |
GET |
Mandatory fields
This section lists the mandatory fields required to create a User or Group:
Users
-
FirstName
-
LastName
-
EmailAddress
-
accessRoleId
-
WorkspaceId
Mappings
The user and group mappings are listed in the tables below.
Table 249: User mapping
| Id |
userid |
| UserName |
userid |
| DisplayName |
firstName + lastName |
| name.GivenName |
firstName |
| name.FamilyName |
lastName |
| emails[].value |
emailAddress |
| Active |
isLocked == false |
| Extension.rolesAndWorkspaces[].accessRoleId |
userRoleWorkspaces[].accessRoleId |
| Extension.rolesAndWorkspaces[].accessRoleName |
userRoleWorkspaces[].accessRoleName |
| Extension.rolesAndWorkspaces[].workspaceId |
userRoleWorkspaces[].workspaceId |
| Extension.rolesAndWorkspaces[].workspaceName |
userRoleWorkspaces[].workspaceName |
Roles
Table 250: Roles mapping
| id |
id |
| name |
name |
| description |
description |
| Type |
type |
|
Meta.Created |
createdAt |
|
Meta.LastModified |
updatedAt |
Workspaces
Table 251: Workspaces mapping
| id |
id |
| name |
name |
| description |
description |
| Status |
Status |
|
Meta.Created |
createdAt |
|
Meta.LastModified |
updatedAt |
Connector limitations
- Create User is a multiple steps operation.
- Once the Create User request is successfully submitted to One Identity Manager, the user will receive an email on the email ID mentioned in the request.
- User must click on the link provided in the email and set a password.
- User is now activated and will be available at the target instance.
- To Create a User, at least one pair of accessRoleId and WorkspaceId must be provided.
- One Identity Manager must have multi-value arrays of string type to hold the values of the User properties: accessRoleId, accessRoleName, WorkspaceId and WorkspaceName.
- Update User is a multiple steps operation.
- Only confirmed Users can be updated.
-
One round of full synchronization is required before submitting the UPDATE request on a newly created User. This must be done to synchronize the User details after activation. This applies to newly created Users only, however existing User UPDATE will work as usual.
- Roles and Workspaces endpoints are used only to retrieve data from target and store it in One Identity Manager and can not to be used to assign or unassign Roles and Workspaces to a User.
- Connector supports cursor pagination and hence TotalResults are not returned.
- Duplicate User CREATE request will return Internal Server Error: 500 with the message System Error: This userid is in use. Choose another email for already existing activated User. However, error 409 is returned if the User is not activated.
-
The pagination scenarios are not tested for Marketo Connector due to unavailability of adequate target system instance.
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.
Synchronization and integration of Workspaces object type with One Identity Manager
For more information, see Synchronization and integration of Workspaces object type with One Identity Manager.
Add Roles ID and Workspaces ID to create and update users for Marketo connector
To create a user successfully using Marketo connector, you must provide valid values for mandatory properties such as Roles ID and Workspaces ID in the request. Roles ID and Workspaces ID are the sub-attributes of the main attribute RolesAndWorkspaces, which is a complex multi-valued string attribute defined under User extensions in the connector schema.
One Identity Manager must have fields where you can enter complex multi-value array values but it does not display such fields by default. However, it is possible to create custom multi-value array fields. For more information, see Creating multi-valued custom fields in One Identity Manager.
NOTE: The above example of creating multi-valued custom fields is one of the various ways to achieve the configuration required for adding Roles ID and Workspaces ID to create and update Users. There may be other ways to achieve this integration based on the customization options that One Identity Manager provides.
Supervisor configuration parameters
The Marketo connector allows you to connect Marketo with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance the services provided by Marketo.
Marketo provides marketing automation software for all types of digital marketing. It provides services to capture the interaction with each customer, enabling users to identify the most profitable channels and campaigns.
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 246: Supported operations for Users
|
Create(Invite) User |
POST |
| Update User |
PUT |
| Delete User |
DELETE |
| Get User |
GET |
| Get All Users |
GET |
| Add RoleAndWorkspace to User |
PUT |
|
Remove RoleAndWorkspace from User |
PUT |
Roles
Table 247: Supported operations for Roles
| Get all Roles |
GET |
Workspaces
Table 248: Supported operations for Workspaces
| Get all Workspaces |
GET |
Mandatory fields
This section lists the mandatory fields required to create a User or Group:
Users
-
FirstName
-
LastName
-
EmailAddress
-
accessRoleId
-
WorkspaceId
Mappings
The user and group mappings are listed in the tables below.
Table 249: User mapping
| Id |
userid |
| UserName |
userid |
| DisplayName |
firstName + lastName |
| name.GivenName |
firstName |
| name.FamilyName |
lastName |
| emails[].value |
emailAddress |
| Active |
isLocked == false |
| Extension.rolesAndWorkspaces[].accessRoleId |
userRoleWorkspaces[].accessRoleId |
| Extension.rolesAndWorkspaces[].accessRoleName |
userRoleWorkspaces[].accessRoleName |
| Extension.rolesAndWorkspaces[].workspaceId |
userRoleWorkspaces[].workspaceId |
| Extension.rolesAndWorkspaces[].workspaceName |
userRoleWorkspaces[].workspaceName |
Roles
Table 250: Roles mapping
| id |
id |
| name |
name |
| description |
description |
| Type |
type |
|
Meta.Created |
createdAt |
|
Meta.LastModified |
updatedAt |
Workspaces
Table 251: Workspaces mapping
| id |
id |
| name |
name |
| description |
description |
| Status |
Status |
|
Meta.Created |
createdAt |
|
Meta.LastModified |
updatedAt |
Connector limitations
- Create User is a multiple steps operation.
- Once the Create User request is successfully submitted to One Identity Manager, the user will receive an email on the email ID mentioned in the request.
- User must click on the link provided in the email and set a password.
- User is now activated and will be available at the target instance.
- To Create a User, at least one pair of accessRoleId and WorkspaceId must be provided.
- One Identity Manager must have multi-value arrays of string type to hold the values of the User properties: accessRoleId, accessRoleName, WorkspaceId and WorkspaceName.
- Update User is a multiple steps operation.
- Only confirmed Users can be updated.
-
One round of full synchronization is required before submitting the UPDATE request on a newly created User. This must be done to synchronize the User details after activation. This applies to newly created Users only, however existing User UPDATE will work as usual.
- Roles and Workspaces endpoints are used only to retrieve data from target and store it in One Identity Manager and can not to be used to assign or unassign Roles and Workspaces to a User.
- Connector supports cursor pagination and hence TotalResults are not returned.
- Duplicate User CREATE request will return Internal Server Error: 500 with the message System Error: This userid is in use. Choose another email for already existing activated User. However, error 409 is returned if the User is not activated.
-
The pagination scenarios are not tested for Marketo Connector due to unavailability of adequate target system instance.
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.
Synchronization and integration of Workspaces object type with One Identity Manager
For more information, see Synchronization and integration of Workspaces object type with One Identity Manager.
Add Roles ID and Workspaces ID to create and update users for Marketo connector
To create a user successfully using Marketo connector, you must provide valid values for mandatory properties such as Roles ID and Workspaces ID in the request. Roles ID and Workspaces ID are the sub-attributes of the main attribute RolesAndWorkspaces, which is a complex multi-valued string attribute defined under User extensions in the connector schema.
One Identity Manager must have fields where you can enter complex multi-value array values but it does not display such fields by default. However, it is possible to create custom multi-value array fields. For more information, see Creating multi-valued custom fields in One Identity Manager.
NOTE: The above example of creating multi-valued custom fields is one of the various ways to achieve the configuration required for adding Roles ID and Workspaces ID to create and update Users. There may be other ways to achieve this integration based on the customization options that One Identity Manager provides.
Supported objects and operations
The Marketo connector allows you to connect Marketo with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance the services provided by Marketo.
Marketo provides marketing automation software for all types of digital marketing. It provides services to capture the interaction with each customer, enabling users to identify the most profitable channels and campaigns.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Users
Table 246: Supported operations for Users
|
Create(Invite) User |
POST |
| Update User |
PUT |
| Delete User |
DELETE |
| Get User |
GET |
| Get All Users |
GET |
| Add RoleAndWorkspace to User |
PUT |
|
Remove RoleAndWorkspace from User |
PUT |
Roles
Table 247: Supported operations for Roles
| Get all Roles |
GET |
Workspaces
Table 248: Supported operations for Workspaces
| Get all Workspaces |
GET |
Mandatory fields
This section lists the mandatory fields required to create a User or Group:
Users
-
FirstName
-
LastName
-
EmailAddress
-
accessRoleId
-
WorkspaceId
Mappings
The user and group mappings are listed in the tables below.
Table 249: User mapping
| Id |
userid |
| UserName |
userid |
| DisplayName |
firstName + lastName |
| name.GivenName |
firstName |
| name.FamilyName |
lastName |
| emails[].value |
emailAddress |
| Active |
isLocked == false |
| Extension.rolesAndWorkspaces[].accessRoleId |
userRoleWorkspaces[].accessRoleId |
| Extension.rolesAndWorkspaces[].accessRoleName |
userRoleWorkspaces[].accessRoleName |
| Extension.rolesAndWorkspaces[].workspaceId |
userRoleWorkspaces[].workspaceId |
| Extension.rolesAndWorkspaces[].workspaceName |
userRoleWorkspaces[].workspaceName |
Roles
Table 250: Roles mapping
| id |
id |
| name |
name |
| description |
description |
| Type |
type |
|
Meta.Created |
createdAt |
|
Meta.LastModified |
updatedAt |
Workspaces
Table 251: Workspaces mapping
| id |
id |
| name |
name |
| description |
description |
| Status |
Status |
|
Meta.Created |
createdAt |
|
Meta.LastModified |
updatedAt |
Connector limitations
- Create User is a multiple steps operation.
- Once the Create User request is successfully submitted to One Identity Manager, the user will receive an email on the email ID mentioned in the request.
- User must click on the link provided in the email and set a password.
- User is now activated and will be available at the target instance.
- To Create a User, at least one pair of accessRoleId and WorkspaceId must be provided.
- One Identity Manager must have multi-value arrays of string type to hold the values of the User properties: accessRoleId, accessRoleName, WorkspaceId and WorkspaceName.
- Update User is a multiple steps operation.
- Only confirmed Users can be updated.
-
One round of full synchronization is required before submitting the UPDATE request on a newly created User. This must be done to synchronize the User details after activation. This applies to newly created Users only, however existing User UPDATE will work as usual.
- Roles and Workspaces endpoints are used only to retrieve data from target and store it in One Identity Manager and can not to be used to assign or unassign Roles and Workspaces to a User.
- Connector supports cursor pagination and hence TotalResults are not returned.
- Duplicate User CREATE request will return Internal Server Error: 500 with the message System Error: This userid is in use. Choose another email for already existing activated User. However, error 409 is returned if the User is not activated.
-
The pagination scenarios are not tested for Marketo Connector due to unavailability of adequate target system instance.
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.
Synchronization and integration of Workspaces object type with One Identity Manager
For more information, see Synchronization and integration of Workspaces object type with One Identity Manager.
Add Roles ID and Workspaces ID to create and update users for Marketo connector
To create a user successfully using Marketo connector, you must provide valid values for mandatory properties such as Roles ID and Workspaces ID in the request. Roles ID and Workspaces ID are the sub-attributes of the main attribute RolesAndWorkspaces, which is a complex multi-valued string attribute defined under User extensions in the connector schema.
One Identity Manager must have fields where you can enter complex multi-value array values but it does not display such fields by default. However, it is possible to create custom multi-value array fields. For more information, see Creating multi-valued custom fields in One Identity Manager.
NOTE: The above example of creating multi-valued custom fields is one of the various ways to achieve the configuration required for adding Roles ID and Workspaces ID to create and update Users. There may be other ways to achieve this integration based on the customization options that One Identity Manager provides.
