Manage products
In Products, you can manage the products that are connected with Cisco Cloud Control.
Use this page to view your connected product ecosystem and establish new connections.
-
Connected: Displays connected products. From here, you can manage the tenants associated with these products.
-
Available to connect: Displays the products that meet these criteria:
-
You are configured as a full admin user for at least one of these products' tenants.
-
These products have not been connected to Cisco Cloud Control yet.
-
Connect multiple product tenants
Cisco Cloud Control supports the connection of multiple product tenants to a single environment. It can include tenants from different products and, when supported, multiple tenants from the same product. For example, you can create an environment that contains three Meraki tenants and two Intersight tenants.
Creating an environment provides these benefits:
-
Eliminates the need to sign in to multiple products. After you have created an environment, you only need to sign in to Cisco Cloud Control to access the relevant products.
These products support the connection of multiple product tenants to a single Cisco Cloud Control environment:
-
Meraki
-
Intersight
-
Nexus Hyperfabric
-
Collaboration Control Hub
-
Splunk Cloud
-
-
Correlates alert and asset data across the products in the environment. You can view and act on this data in Cisco Cloud Control to monitor and troubleshoot those products.
Connecting multiple product tenants affects these three areas:
Navigate product tenants within an environment
When multiple product tenants are configured for the same product, you can switch between them in two locations:
-
In the top navigation bar, select the pinned product.
-
Open Cisco Cloud Control’s Main menu and then select the product to view the list of available environments.
View data across connected product tenants
A Cisco Cloud Control environment displays alert, inventory, and topology data received from all of its connected product tenants. For example, an environment that is connected to multiple Intersight tenants displays the assets from all of these tenants in the same inventory and topology. It also displays the alerts generated for these tenants.
Maintain RBAC settings for connected product tenants
When an environment is connected to multiple product tenants, the RBAC settings for each connected tenant are maintained. Cisco Cloud Control only allows you to see and manage the assets you are entitled to:
-
An administrator can see all assets across all connected product tenants.
-
A member linked to several tenants may be entitled to only a subset of those assets.
Environment switching considerations
When you switch environments, consider these factors:
-
Permissions and roles: Access is governed by your assigned permissions. You will only see and be able to switch to environments for which you have the appropriate access.
-
Session security: For security, your session has a defined timeout. If your token expires, you may be required to re-authenticate regardless of your previous activity.
-
Connected products: The feature is optimized for products connected to Cisco Cloud Control. If you switch to an environment that is not associated with your current product, you may be redirected to the main Cisco Cloud Control dashboard.
-
Cross-product authentication: When switching environments, Cisco Cloud Control may open a pop-up window to handle authentication of the product launch. Ensure your browser is configured to allow pop-ups from the Cisco Cloud Control domain.
When you switch between products in an environment, Cisco Cloud Control exchanges tokens in the background. You are then transitioned to the product tenant without needing to re-enter your credentials.
Troubleshoot environment switching
Use these possible solutions to troubleshoot environment-switching issues:
-
Switch takes time: A brief loading period is normal while the system verifies your credentials across products.
-
Environment does not appear: Ask your administrator to verify that your user account is provisioned and linked to the product.
-
Switch fails or hangs: Check your browser pop-up settings and ensure that pop-ups are allowed for Cisco Cloud Control.
Connect the product to Cisco Cloud Control
Follow these steps to connect a product to Cisco Cloud Control.
To complete this operation, you must be an Admin user for the product you want to connect.
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
In Available to connect, select Connect for the relevant product.
Select tenants opens. -
In Eligible tenants, select the tenants you want to add.
Only product tenants that meet both of these conditions appear here:
-
You have full admin access to the tenant.
-
The tenant is not connected to another environment.
-
-
Select Connect.
-
Select Connect tenant to confirm this operation.
Manage tenants for a connected product
Follow these steps to add or disconnect tenants from a product that is connected to Cisco Cloud Control.
-
You must be an Environment Admin user to complete this procedure.
-
You can only connect or disconnect tenants from products to which you have full admin access.
-
Cisco Cloud Control supports the configuration of multiple tenants for the products listed in Connect multiple product tenants. These are the only products you can only add additional tenants to.
-
When you disconnect products from an environment, sign-in options change:
-
You disconnected the last tenant for a product: You can no longer sign in to the environment through that product.
-
You disconnected every product associated with the environment: You can sign in to the environment only with your Cisco Cloud Control account.
If you do not have a Cisco Cloud Control account, you are prompted to create one.
-
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
In Connected, select the relevant product to view its tenant list.
-
Add tenants:
-
Select Add tenant.
Select tenants opens. -
In Eligible tenants, select the tenants you want to add.
-
Select Connect.
-
Select Connect tenant to confirm this operation.
-
-
Disconnect tenants:
-
For each tenant you want to remove, select its corresponding trash icon.
-
Select Disconnect to confirm the removal of the tenant.
-
Browse all products
Follow these steps to open All products, which displays every product you can connect to Cisco Cloud Control.
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
Select Browse all products.
All products opens, consisting of these sections:-
Additional products: Only an admin user for these products can connect it with Cisco Cloud Control. For more information, refer to Invite a product admin to connect.
-
On-premise products: Select Set up to connect Catalyst Center with Cisco Cloud Control. For more information, refer to Connect Catalyst Center.
-
Invite a product admin to connect
If you do not have admin access to a product or its tenants, you can invite someone who does to connect them to your Cisco Cloud Control environment. The invitee joins your environment as an Environment Admin and can connect any eligible product tenants they have admin access to.
-
This flow is separate from the Add user flow described in Manage users. Complete this flow to invite a product admin to connect their product. Complete the Add user flow to give a user access to Cisco Cloud Control.
-
Cisco Cloud Control does not verify whether the email address you enter belongs to an existing account or whether that user has Admin permissions in the selected product. To ensure successful environment setup, before you send the invitation, confirm that you have entered the exact email address of an existing administrator for that product.
Follow these steps to invite a product admin to connect a product:
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
Select Browse all products.
-
In Additional products, select Invite admin for the relevant product.
-
In Invite an admin of <product name>:
-
Enter the admin’s First name, Last name, and Email address.
-
Select Send invite to send the admin an invitation email.
-
Connect to the invited environment
If you have admin access to a product, such as Nexus Hyperfabric, and you receive an email invitation to connect it to Cisco Cloud Control, follow these steps to join the environment and choose which product tenants to connect. Setting up your Cisco Cloud Control account does not change your existing roles or permissions in the product.
See Cisco Cloud Control Getting Started for an overview of Cisco Cloud Control and any prerequisites for your product.
-
Open the email and select one of these buttons:
-
If you do not have a Cisco Cloud Control account, select Activate account.
-
If you already have a Cisco Cloud Control account, select Sign in to Cloud Control.
-
-
Follow the prompts to activate your Cisco Cloud Control account and sign in. If you are asked to create a password and set up Duo, do so.
You are added as an Environment Admin user. After you sign in, the Products page opens with the invited environment selected. -
Complete the steps applicable to your situation:
To connect a new product with Cisco Cloud Control:-
In Available to connect, locate your product’s tile and select Connect.
Select tenants opens. -
In Eligible tenants, select the tenants you want to add.
To add tenants to a product that is already connected to Cisco Cloud Control:
-
In Connected, select the relevant product to view its tenant list.
-
Select Add tenant.
Select tenants opens. -
In Eligible tenants, select the tenants you want to add.
-
-
Select Connect.
-
Select Connect tenant to confirm this operation.
Your product is now connected with Cisco Cloud Control.
Create a new environment
Follow these steps to create a new environment in Cisco Cloud Control and log into it.
-
You must be a Environment Admin user to complete this procedure.
-
If you stop before you create a password, you cannot resume this procedure. To create a new environment, restart the procedure from the beginning.
-
Open the environment switcher, then select Create a new environment.
-
Enter a name for this environment, then select Create.
-
Create a password for the new environment:
-
Select Set up Cloud Control password.
A six-digit confirmation code is sent to the email address configured for the Cisco Cloud Control admin user. -
Enter the confirmation code, then select Verify.
-
Enter the password you want to set for your user account, then select Next.
-
Select I have set my password - continue sign-in.
Products opens with the environment you just created selected in the environment switcher. -
To connect a product with this environment, complete the steps described here.
-
Manage users
In Users, you can view and manage the users who have access to Cisco Cloud Control and connected products.
If you are using an external Identity Provider (IdP) and notice stale administrator entries, those entries are not a security vulnerability. This behavior occurs because Cisco Cloud Control does not currently integrate with your IdP lifecycle management feature. Cisco defers to your IdP as the authoritative source for user access control.
Add a user
Add users to give them access to Cisco Cloud Control. Their assigned role determines what they can view and manage.
Complete these steps to add a user to Cisco Cloud Control.
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
Select Users.
-
Select Manage users > Add user.
-
In Add user, complete these steps:
-
Enter the email address of the user you are adding. Then select Next. 9
-
(Optional) Enter the first and last name of the user. Then select Next.
-
(Optional) Assign one of these admin roles to the new user:
-
Environment Admin: Can configure and manage all environment-level settings.
-
Environment Viewer: Can view all environment-level settings, but cannot change them.
-
Integration Admin: Can manage cross-product and third-party integrations in Cisco Cloud Control, but does not have platform administration rights.
-
By default, the Member role is configured for all Cisco Cloud Control users.
-
Environment Admin users can see all data within the Cisco Cloud Control environment. However, they cannot access individual product dashboards (such as Meraki or Intersight) for which they do not have explicit product permissions.
-
You can configure the Environment Viewer and Integration Admin roles for the same user.
-
-
Select Next.
-
In Summary, confirm that the information you entered for the new user is correct. Then select Add user.
Cisco Cloud Control sends the user you added an email that prompts them to activate their account. That user’s details will be available in Users after they sign in for the first time.
If the user already has an active Cisco Cloud Control account, they may receive a password reset email instead of an invitation email.
-
-
To grant this user access to Nexus Dashboard data in Cisco Cloud Control, follow the steps in Configure Nexus Dashboard access for AI Canvas.
Search for a user
Search for a Cisco Cloud Control users and view their details by completing these steps.
-
Select the Main menu
and choose Admin Console. -
Use Search to find a user by name or email address.
-
Select the products and roles you want to use to filter the table entries.
-
In Display name, select a user’s link to view their details.
Manage a user
Follow these steps to manage a Cisco Cloud Control user.
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
Select Users.
-
Select
, then select one of these options:-
View user details: View the user’s profile, their configured roles, and the products they can access.
You can also select a user’s link in Display name to view this information.
-
Edit profile: Update the user profile information.
-
Edit role assignments: Change the role assignments for that user.
-
Customize the information displayed on Users
Follow these steps to customize the information that is displayed on Users.
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
Select Users.
-
Select
to customize the table density and column settings.
Invite an administrator to add a tenant to your environment
If you and another administrator manage two different products, you can consolidate the tenants associated with these products into a single Cisco Cloud Control environment. For example, you manage an Intersight tenant, and another administrator manages a Security Cloud Control tenant. By connecting these product tenants to a single environment, both products can contribute alert, inventory, and topology data to Cisco Cloud Control.
To connect these product tenants, invite the other product administrator to Cisco Cloud Control and assign them the permissions required to add their product tenant to your environment.
The relevant workflow consists of two steps:
-
You invite the administrator for another product by setting them up as a Cisco Cloud Control user.
-
That administrator adds their product tenant to your environment.
Invite an administrator to Cisco Cloud Control
-
Select the Main menu
and choose Admin Console.By default, Products is displayed.
-
Select Users.
-
Select Manage users > Add user.
-
Enter the administrator’s email address. Select Next.
-
(Optional) Enter the administrator’s first and last name. Select Next.
-
Assign the administrator the Environment Admin role and then select Next.
-
Confirm that the information you entered for the administrator is correct. Then select Add user.
The administrator receives an email inviting them to activate their Cisco Cloud Control account.
-
If the administrator already has an active Cisco Cloud Control account, they may receive a password reset email instead of an invitation email.
-
Account activation emails may display inconsistent formatting. In the light theme, the Activate Account button may appear disabled, but it remains functional. For assistance, go directly to the Cisco Contact Us website.
-
If the administrator is already an active Cisco Cloud Control user, ensure that they are configured with the Environment Admin role.
-
Add a tenant to an environment created by another administrator
After activating their account and logging into Cisco Cloud Control, the invited administrator can see your environment in their environment switcher. They can then add their product tenant to this environment by completing the steps described in Manage the tenants for a connected product.
User access after connecting product tenants to an environment
Connecting product tenants managed by two different administrators to the same Cisco Cloud Control environment does not change user permissions:
-
Users can see and access only the products for which they have a user account.
-
Users with access to both products can see both, and Cisco Cloud Control’s Inventory and Topology draw data from both.
Set up SSO
Complete these setup tasks to configure single sign-on (SSO) for Cisco Cloud Control users.
-
Configure an IdP using either SAML or OpenID Connect.
Create a domain
Follow these steps to create a domain.
-
Select the Main menu
and choose Admin Console.By default, Users is displayed.
-
Select Domains.
-
Select Add a domain.
-
Enter your domain or subdomain name and select Add domain.
-
Copy the verification token into your DNS TXT record.
-
If your DNS host supports only one TXT record, add the token on a separate line.
-
If your DNS host supports multiple records, add your token on a single line in a separate TXT record.
-
-
Choose who adds the DNS TXT record:
-
If you can add the DNS TXT record, add it to your DNS server.
-
If another administrator configures your DNS server, send the DNS TXT record to that administrator.
-
-
Select Done.
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.
Configure an IdP using SAML
SAML provides a framework for IdPs and service providers to communicate with each other for federated identity and SSO. You can set up a SAML IdP by manually entering IdP metadata or uploading metadata to the Admin Console.
Follow these steps to configure an IdP using SAML.
-
Select the Main menu
and choose Admin Console. -
Select Identity Providers.
-
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:
-
Fill out configuration form: Manually enter your IdP metadata. Then proceed to Step 7.
-
Upload your IdP’s metadata: Upload an XML file containing your IdP metadata. Then proceed to Step 8.
-
-
If you selected Fill out configuration form:
-
Enter your Entity ID (SAML Identifier).
-
Enter your Single sign-on URL.
-
Select a binding method: HTTP-Post or HTTP-Redirect.
-
(Optional) Enter your Single sign-out URL.
-
(Optional) Select a binding method: HTTP-Post or HTTP-Redirect.
-
Check the check box to enable Sign SAML request.
Select this check box if your IdP requires authentication requests to be signed.
-
Select a NameID format.
You can select one of these options:
-
urn:oasis:names:tc:SAML1.1:nameid-format:emailAddress(default): This format uses your email address as your NameID. -
urn:oasis:names:tc:SAML2.0:nameid-format:transient: This format generates a temporary, one-time NameID for each authentication. -
urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified: This format indicates that no specific NameID format is requested, allowing your IdP to determine or use an appropriate format.
-
-
Upload your IdP certificate files.
If your IdP uses multiple signing certificates, you can upload up to two IdP certificate files in
.pemor.cerformat. -
Select Next.
-
-
If you selected Upload your IdP’s metadata:
-
Upload an XML file containing your IdP metadata.
When uploading the metadata file, there are two ways to validate the metadata from the customer IdP:
-
Not signed, self-signed, or private CA-signed IdP metadata file: Your IdP provides a self-signed private CA or doesn’t provide a signature for its metadata. This option is less secure.
-
Signed by a public certificate authority: Your IdP provides a signature in the metadata that is signed by a Public Root CA.
Only upload metadata generated by your IdP. Uploading the wrong metadata file will cause SSO failure and might lock all administrators out of the account.
-
-
Select Next.
-
-
(Optional) Configure SAML attributes and settings.
By default, the SAML IdP uses the
uidattribute 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.
Configure an IdP using OpenID Connect
Use OpenID Connect (OIDC) to set up SSO using your identity provider. OIDC is built on the OAuth 2.0 framework and supports secure authentication through encrypted tokens and built-in certificate validation.
When you set up OpenID Connect with Entra ID or an IdP where the email is not a permanent identifier, we recommend that you use the externalId linking attribute to map to a unique identifier. For Entra ID, we suggest mapping OIDC to externalId. If the email you enter does not match the linking attribute, you are prompted to verify your identity or create a new user with the correct email address.
Follow these steps to configure an IdP using OpenID Connect.
-
Select the Main menu
and choose Admin Console. -
Select Identity Providers.
-
Select Add an IdP.
-
In Add an Identity Provider, select OpenID Connect as your IdP and select Next.
-
Enter your IdP information.
-
Enter your IdP Name.
-
Enter your Client ID. This is the unique ID that identifies you and your IdP.
-
Enter your Client Secret. This is the password that you and your IdP know.
-
Select the scopes you want to associate with your IdP.
OpenID and Email are selected by default.
-
-
Select one of these methods to add endpoints:
-
Use the discovery URL: Enter the discovery URL for your IdP.
This URL automatically populates the necessary endpoints for OIDC single logout (SLO).
-
Manually add all endpoint information: Select this option if your IdP does not support discovery URLs. Provide these details:
-
Issuers (comma-separated): Enter one or more issuer URIs, separated by commas.
-
Authorization endpoint: URL to start the authorization flow.
-
Token endpoint: URL to retrieve access tokens.
-
(Optional) JWKS URI: URL to retrieve the JSON Web Key Set.
-
(Optional) Userinfo endpoint: URL to retrieve user profile information.
-
(Optional) End session endpoint: URL to support single sign-out.
-
-
-
(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.
Create a routing rule
Follow these steps to create a routing rule.
-
Select the Main menu
and choose Admin Console. -
Select Identity Providers.
-
Select Routing rules > Add a routing rule.
-
Provide these details for a routing rule:
-
Rule Name: Enter a name for the routing rule.
-
Select a routing type: Select Domain or Group.
If you select Domain, your domain must be verified. For more information, refer to Create a domain.
-
If these are your domains/groups: Select domains or groups within your organization.
-
Then use this identity provider: Select IdP.
-
Allow MFA for this rule: Toggle MFA on or off for this rule.
-
-
Select Add.
-
Select
> Activate.
For any routing rule that has been created, you can select
and complete these tasks:-
Edit routing rule: Allows you to select a different IdP and toggle MFA on or off.
-
Deactivate: Deactivate the selected rule.
-
Service provider certificates
From Service providers, you can manage the service provider certificates used by Cisco Cloud Control.
Complete any of these tasks to manage service provider certificates:
The numbered callouts identify where in Service providers you can complete these tasks.
-
1: View the Redirect URI for your OIDC provider.
-
2: Download the metadata for your IdP.
-
4: View your certificate.
-
5: Download the certificate or its metadata.
Add or renew your service provider certificate
Follow these steps to add or renew your service provider certificate.
-
Select the Main menu
and choose Admin Console. -
Select Identity Providers > Service providers (SP).
-
Select Add or renew certificate.
-
Select one of these options:
-
Self-signed by Cisco: We recommend this choice. Let Cisco sign the certificate so you only need to renew it once every five years.
-
Signed by a public certificate authority: The customer IdP provides a signature in the metadata that is signed by a Public Root CA. This option is more secure, but you need to update the metadata frequently unless your IdP vendor supports trust anchors.
-
-
Select Save.
Enable AI model training
In Data Preferences, you can set whether the data from your tenant’s interactions with AI Canvas and AI Assistant are used to train and improve Cisco Cloud Control’s AI models. This data can include prompts you have run, responses to those prompts, files you have uploaded, and data retrieved from applicable Cisco offers. By enabling this option, you can help improve both the accuracy and relevance of Cisco Cloud Control’s AI experience.
Only users configured with the Environment Admin role can complete this operation. Users configured with the Environment Viewer role can view this setting, but are not able to change it.
To toggle this setting on or off:
-
Select the Main menu
and choose Admin Console.By default, Users is displayed.
-
Select Settings.
-
In Data Preferences, toggle AI model training on or off.
By default, this option is enabled. -
When prompted, select either Opt in or Opt out to confirm your setting change.
-
Data Preferences indicates the last time your tenant’s AI model training setting was changed, as well as the user that made this change. Select View change history to open the Audit Log and confirm the change.
-
To get more information on how Cisco uses this data:
-
Open Cisco’s Trust Portal.
-
View the AI Assistant and AI Canvas offer disclosure documents.
-
Audit logs
Cisco Cloud Control creates a log file whenever a user makes a system change or an event takes place. Use Audit Log to view details for these changes and events, as well as export available log files.
Use these tasks to work with audit logs:
View audit log files
Follow these steps to view audit log files for events or system changes.
-
Select the Main menu
and choose Admin Console.By default, Users is displayed.
-
Select Audit Log.
-
Filter and customize the information that the audit log displays:
-
In Search, enter a text string.
-
Select values from the available drop-down lists.
You can choose a specific period of time, as well as an event type (likeAuthif you only want to view which users logged in to Cisco Cloud Control and when). -
(Optional) Select
to customize the table density and displayed columns.
-
-
Select a log file’s date and time to view its details.
If a user does not have a display name configured in CUI, the system defaults to their email address.
You can also:
-
Copy any of the details associated with this change or event.
-
Select Copy to copy and paste the contents of this log file to a local file.
-
Generate an audit report
Follow these steps to generate an audit report.
-
Select the Main menu
and choose Admin Console. -
Select Audit Log.
-
Select Generate report to download the audit log data as a CSV file.