Troubleshooting Guide › Tenant Deployment Issues

Tenant Deployment Issues

The section provides information to troubleshoot tenant deployment related issues.

This section contains the following topics:

Tenant Creation Issues

CA Directory Web Services Issues

“Unable to process your Request now” Error Message When Accessing the User Console

Credential Handling Service Login Issues

Internal Error When Logging in with PKI with risk or with OTP with risk

Tenant Creation Issues

When creating tenants, several general recommendations exist:

• When experiencing tenant creation issues, check the JBoss log of the Cloud Service Provider (CSP) to see if the creation has started. For example, was the CSP able to contact the Hosting container? Depending on the content, it can helpful to view the JBoss log of the Identity Management server and then the CA IAM Connector Server daily log.
  • The CSP JBoss log is located here:

    /opt/CA/siteminder/adminui/[JBOSS]/server/default/log/server.log

  • The Connector Server log is located here:

    /opt/CA/IdentityManager/ConnectorServer/jcs/logs/jcs_daily.log

  • The JBoss log is located here:

    IM JBoss log: /opt/[JBOSS]/server/all/log/server.log

  Note: [JBOSS] varies, depending whether you are using the JBoss EAP or Community version.

• Setting com.ca.voyager to DEBUG in JBoss of both CSP console and CA IdentityMinder can provide additional helpful information.
• When creating a new tenant, do not include the word tenant in its name.

Check the follow settings in the CSP Console:

• If the CA IAM Connector Server is installed on a separate server, then make sure that SiteMinder Provisioning Server Tenant Service Host is set to the CA IAM Connector Server host name in the Hosting Container.
• In the Hosting Container, list all host names for CA IdentityMinder, SiteMinder Provisioning Server, and the CA IAM Connector Server in the section for Tenant DSA Router Hostnames. If the CA IAM Connector Server is installed on the SiteMinder Provisioning Server, list the host names of the SiteMinder Provisioning Server instead.