Cisco Cloud Control Administration

Select and choose Admin Console.

By default, Users is displayed.

Select Manage users > Add user.

In Add user, complete these steps:

To grant this user access to Nexus Dashboard, complete the steps in Configure Nexus Dashboard access.

Select and choose Admin Console.

Use Search to find a user by name or email address.

Select Products and then select relevant accessible products to filter the results.

Select a user name to view the user details.

Select and choose Admin Console.

Select the display name to view the user details.

You can also select to open a menu with the same options.

Select Actions, and then select one of these options:

Select and choose Admin Console.

Select to customize the table density and column settings.

Select and choose Admin Console.

Select Manage users > Manage Nexus Dashboard access.

To change the settings for a user who already has access to Nexus Dashboard, select > Manage assignment. Then proceed to the role assignment step.

Select Assign.

In Assign user, complete these steps:

From the top navigation bar, select the current tenant name.

Select an available tenant.

If you move between linked tenants or products within the same realm, Cisco Cloud Control performs a background token exchange. You are then transitioned to the new environment without needing to re-enter your credentials.

Select and choose Admin Console.

By default, Users is displayed.

Select Tenants.

Find a tenant:

The tenant list is filtered based on your selections.

Review the tenant information:

Select and choose Admin Console.

By default, Users is displayed.

Select Tenants.

Select Group tenants.

The system displays the products for which you have full administrative access.

Select the tenants you want to include in the group, choosing one tenant for each product.

When adding a tenant to a group for the first time, you may be prompted to sign in to each individual tenant. This sign-in step authenticates your identity across different product environments and obtains the necessary tokens.

Enter a name for the group.

Select the check box to acknowledge that users who sign in to any tenant in the group can access all other grouped tenants.

Select Save.

When tenants are grouped, Cisco Cloud Control uses one tenant ID as the primary identifier. Cisco Cloud Control does not automatically delete the IDs of the other tenants that joined the group.

Select and choose Admin Console.

By default, Users is displayed.

Select Tenants.

For the tenant you want to add to a group, select .

Add this tenant to an existing group.

Select and choose Admin Console.

By default, Users is displayed.

Select Tenants.

For the tenant group you want to rename, select the pencil icon.

Rename the tenant group.

Select and choose Admin Console.

By default, Users is displayed.

Select Domains.

Select Settings > Manage domains.

Select Add a domain.

Enter your domain or subdomain name and select Next.

Copy the verification token into your DNS TXT record.

Choose who adds the DNS TXT record:

Select Add domain.

Your domain appears in your list of domains with the status Pending. When it’s verified, the status changes to Verified.

After the domain is verified, the TXT record is no longer required, and you can remove the verification token from your DNS server.

If verification fails, the error is cached by your DNS server. Your DNS server clears the cache after the time specified in the Time To Live (TTL) setting. You must wait to try again after the DNS server clears the cache. You can add the verification token again and request verification for the domain.

Select and choose Admin Console.

Select Domains.

Select Settings > Manage IdPs.

Select Add an IdP.

In Add an Identity Provider, select SAML as your IdP and select Next.

Select one of these methods to connect your IdP:

If you selected Fill out configuration form:

If you selected Upload your IdP’s metadata:

(Optional) Configure SAML attributes and settings.

By default, the SAML IdP uses the uid attribute to identify the user when it sends authentication data to Cisco Cloud Control. If the IdP supports other NameID configurations, you can modify this configuration.

Select Add IdP.

If this is the first IdP you have configured, the IdP is saved as your default IdP, and a default routing rule is created.

Select and choose Admin Console.

Select Domains.

Select Settings > Manage IdPs.

Select Add an IdP.

In Add an Identity Provider, select OpenID Connect as your IdP and select Next.

Enter your IdP information.

Select one of these methods to add endpoints:

(Optional) Check Allow the session to automatically sign out if you want to enable automatic sign-out.

Select Add IdP.

If this is the first IdP you have configured, the IdP is saved as your default IdP, and a default routing rule is created.

Select and choose Admin Console.

Select Domains.

Select Settings > Manage IdPs.

Select Routing rules > Add a routing rule.

Provide these details for a routing rule:

Select Add.

Select …​ (next to your new routing rule), then select Activate.

Select and choose Admin Console.

By default, Users is displayed.

Select Audit Log.

Select the type of log files that you want to view:

Find the audit log:

The audit log information is filtered based on your selections.

Select the date and time of a log file to view more details about it.

If a user does not have a display name configured in CUI, the system defaults to their email address.

You can also:

Select and choose Admin Console.

Select Audit Log.

Audit Log displays log file information for either Identity and Access or Admin Activity.

Select Generate report to download the audit log data as a CSV file.