Controller Tenant User Management Overview
Splunk AppDynamics user credentials for SaaS and on-premises deployments are managed according to the authentication options selected in Settings > Administration > Authentication Provider. There are three user authentication options:
Authentication Provider | User Type | Description |
---|---|---|
Cisco Customer Identity | Local User |
Note: Managing a Local User through the Controller Tenant UI affects permissions for that Controller Tenant only. The user account retains Active status with existing permissions on other associated Controller Tenants. Use the Account Management Portal to fully deactivate or edit an account for all
Splunk AppDynamics components and Controller Tenants simultaneously.
|
LDAP | LDAP User |
|
SAML | SAML User |
|
With Splunk AppDynamics SaaS , when you add a new local user through the Controller Tenant UI, an email is sent to that user's valid address prompting them to create their own profile name and password. The user's email serves as their username. Only the account user can create their own password. Once completed, an account with the proper credentials is added to the Controller Tenant and authenticated through the Cisco Customer Identity (IdP) providing the user unified access to the Account Management Portal, University, Community, and role-specific functions on the Controller Tenant UI.
With an on-premises deployment, when you add a new local user through the Controller Tenant UI, an account with the proper credentials is created and stored on that Controller Tenant.
You can create and manage users, groups, roles, and permissions on the corresponding page through Settings >Administration. See Manage Controller Tenant Users and Groups and Manage Custom Roles for Splunk AppDynamics.