With TSNA and enabling LDAP authentication, the sysadmin account is disabled.
At least one AD domain account is created. This account acts as the TrueSight Network Automation administrator because the default system administrator account, sysadmin cannot log on after TrueSight Network Automation is configured for AD authentication.
You might need to create a duplicate adapter in TSO - one for accessing TSNA, and one for accessing Remedy - that uses different credentials. You might also look at using shared SSL keys or something similar (RSSO?) to eliminate the need for direct logins.
Hope this helps!
Thank you for your reply. We already have 2 different adapters for TSNA and Remedy i.e. BCAN Adapter and ARS Adapter.
The Change Request is created in ITSM. Once the change request is approved, TSO is not able to login in TSNA using the Admin account (AD domain Account for eg. LDAPAdmin). TSO is using the webservice for login (doLogin webservice).
Could you please help on this.
In order to log in to TSNA the user needs to :
1) exist in the TSNA Database with the appropriate rights for what you want that user to be able to do
2) exist in the AD Database in the location you have designated in the Userbase settings you configured as part of the TSNA External authentication.
So if you want to use the user LDAPAdmin, your TSNA Administrator will need to add this user as a TSNA user and your AD administrator will need to make sure the user is found in the userbase for username/password authentication.
Are you defining your login credentials within the adapter? Are you overriding those credentials within your workflow? Can you step out the workflow process in terms of concept? i.e. - approve change, execute workflow to update TSO or TSNA, etc. Without knowing the specifics of your configuration and workflow, I'm left to guess that that the credentials that are being used are being overridden
Thanks for your reply. We tried with TSNAAdmin@domain.com user as well. This is the administrator user of TSNA. We gave this user in BCANAdapter configuration. But still we got the same error in TSO processes log. We also tried 'doLogin' operation through development studio with this user which also failed with same error.
We are able to do login through this TSNAAdmin user by accessimg TSNA URL in the browser. But through TSO it is failing to login.
Does the authentication through TSO checks only for users locally and not in the AD database?
Thanks and Regards,
1 of 1 people found this helpful
Saurabh Pasalkar have you reviewed the BCAN Automation Adapter login documentation?
We have followed the steps given in the BCAN adapter config document. It was work in fine with sysadmin. But problem occurred when we integrated with AD.
Also in the workflows, I am not sure where we need to give TSNA credentials. We only need to give the ARS credentials.
We have content pack 20.18 installed for this change management integration.
Could you please tell where in workflow the TSNA credentials are getting overridden?
1 of 1 people found this helpful
Meeta Lalwani why are you marking the question as answered? The original question, at least from what I've read in this conversation, has not been answered. My replies have directed Saurabh Pasalkar towards documentation, but there have been no replies that have been posted stating that they have answered the question.
Apologies, I only wanted to mark it as helpful.
Have you tried modifying the TSO(AO) adapter called “BCANAdapter”. You need to provide LDAP credentials for username and password. Once done, integration should work seamlessly.