Troubleshoot SecureX

You may experience errors, warnings, and issues while attempting to use CDO in conjunction with SecureX. For issues seen in the SecureX UI, you must use the SecureX documentation. See SecureX's Support for more information.

To open a case about the SecureX ribbon functionality within CDO, or about a tenant accessibility to the SecureX ribbon, see CDO Cisco TAC for more information. You may be asked to provide your tenant ID.

SecureX UI Troubleshooting

I see duplicate CDO modules in my SecureX dashboard

You can manually configure multiple modules of a singular product in SecureX. For example, if you have multiple CDO tenants, you can create one CDO module per tenant. A duplicate module implies that there are two separate API tokens from the same CDO tenant. This redundancy can cause confusion and clutters the dashboard.

If you happened to manually configure a CDO module in SecureX and then also chose to Connect SecureX in CDO's General Settings page, this can cause one tenant to have multiple modules in SecureX.

As a workaround, we recommend removing the original CDO module from SecureX and continue monitoring CDO performance with the duplicate module. This module is generated with a more robust API token that is more secure, and compatible with the SecureX ribbon.

CDO UI Troubleshooting

To open a case about the CDO module within SecureX, see the Support section of SecureX's Terms, Privacy, Support for more information.

OAuth Error

You may encounter an oAuth error with this message: "The user does not seem to have all the required scopes or sufficient privilege." If you experience this issue, consider the following possibilities:

  • Your account may not be activated. See https://visibility.test.iroh.site/ and use your registered email address to see if your account is activated or not. If the account is not activated, your CDO tenant may not be merged with SecureX; you must contact Cisco TAC to resolve this issue. See Contact Cisco TACfor more information.

I logged into SecureX with the wrong organization credentials

If you opted to send CDO events to SecureX with the Connect SecureX option in the Tenant Settings section of the General Settings page but used the wrong credentials to log into SecureX, you may see events from the wrong tenant show up in your SecureX dashboard.

As a workaround, click Disconnect SecureX in the General Settings page in CDO. This terminates the read-only API user used to send and receive information to the SecureX organization, and thusly the SecureX dashboard.

You must then re-enable Connect Tenant to SecureX and use the correct organization login credentials when prompted to log into SecureX.

I logged in to the ribbon with the wrong account

At this time, if you log into the ribbon with the wrong account information, you cannot log out of the ribbon. You must open a case in Support Case Manager to manually reset the ribbon login.

Unable to launch the SecureX Ribbon

You may not have access to the appropriate scopes; you must contact Cisco TAC to resolve this issue. See Contact Cisco TACfor more information.

For additional information on how the SecureX ribbon operates, see SecureX ribbon documentation.