BMC Helix IT Operations Management (ITOM) Deployment: OnPrem - How to resend a Tenant Activation email using the TCTL utility - INCLUDES VIDEO

Knowledge Article

BMC Helix IT Operations Management (ITOM) Deployment: OnPrem - How to resend a Tenant Activation email using the TCTL utility - INCLUDES VIDEO
BMC Helix IT Operations Management (ITOM) Deployment: OnPrem - How to resend a Tenant Activation email using the TCTL utility.
BMC Helix Operations Management OnPrem Containers
Helix on-prem - ADE platform
All ITOM Version
BMC Helix Operations Management OnPrem Containers
Helix on-prem - ADE platform
All ITOM Version
As part of the BMC Helix IT Operations Management (ITOM) On-Prem Deployment process, two emails will be sent to the TENANT_EMAIL email address specified in the infra.config file:
 
  • The first email will invite the Admin user to activate their BMC Helix Portal account.
    It will contain the BMC Helix Portal URL and the user name, which is the service account name.
  • The second email will confirm that the License Account is activated

If this step fails, or either of the expected emails are not received, how can this step be rerun manually after the deployment?



Follow the steps below to send the tenant activation email using the TCTL utility

1. Download the TCTL Utility from BMC Electonic Product Distribution (EPD)

Refer to the following documentation to downloading and configuring the tctl utility

2. Configure the "\tctl\config" by referring to the above documentation steps

Example config file: 
appurl: https://tms-support-purple.example.com
clientid: 7cab57b4-08b8-4bbc-8644-b86a6ca30b72
clientsecret: MIIEvAIB....
enableauth: true
rssourl: https://lb-support-support-purple.example.com/rsso

Note 1: The appurl value should not contain a trailing "/tenant" value. The kubectl command referenced in the doc will return the appurl with a trailing "/tenant" which needs to be removed from the value placed in the config file.
Note 2: The rssourl should contain a trailing /rsso value as shown in the above example.


3. Once the tctl "config" file is configured successfully then, use one of the following two options to resend the activation email:
 


Option 1: If the user can wait 72 hours since the initial attempt to send the activation email was made 

If 72 hours have passed since the deployment completed and the sending of the initial activation email was attempted but failed, then, once the underlying issue for the email failure has been resolved, the simplest option is to run the following tctl commands:

  • tctl login
  • tctl get tenant
  • tctl resume tenant <tenant ID> 


This will resume the tenant activation using the same email address specified in infra.config


Option 2: If the user does not wish to wait 72 hours since the first attempt to send the activation email was made  

Once the underlying issue for the email failure has been resolved, specify a new Admin user using the following sequence of tctl commands:
 

  • tctl login
Default tms relam admin user RSSO credentials are: admin/bmcAdm1n1#

 

  • Generate the firstuser JSON template file:
tctl template create-firstuser
 
  • Update the generated create-firstuser.json file with the required first name, last name, login id and email address:
vi create-firstuser.json

 
image.png

  • Run the "create firstuser" command to create the new Admin user. The emails will be sent to the email address specified in the firstuser.json file. 
tctl create firstuser <tenantid> -f <user json file>
 
Example output:
 
Example output:
tctl create firstuser 1097259844 -f create-firstuser.json
Using config file: C:\Users\<>\Downloads\tctl_10252021\tctl\config
HTTP Response Status: 201 Created
Response: {
"login_id": "user1"
}
  • Display details of the new Admin user:
tctl get firstuser <tenantid>



Troubleshooting:

If the expected emails are still not received, review the tms, tas, ims and rsso pod logs.

To get the pod and logs please refer to the below steps for the tms, tas, ims and rsso:
  
kubectl get pod -n <namespace> | grep -i tms
kubectl logs <pod_name> -n <namespace> > /tmp/tms-pod-logs.txt



Alternative methods to get the Tenant ID:

- From the deployment log

User-added image

-  Running “tctl get tenant” which will show the tenant ID (the tenant should be in an active state to use this option)

User-added image

- Tenant ID visible ion the RSSO Tenant page

User-added image
 
 
 
 
 
Refer to the following knowledge article to configure and start using the TCTL utility - here

Refer to the following knowledge article to check and collect Pod or Service Logs in OnPrem Deployment - here
BMC Helix Operations Management OnPrem Containers
Helix on-prem - ADE platform
All ITOM Version
Attachment(s):