This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Server Automation Suite
BMC BladeLogic Server Automation Suite
The following error is encountered when launching a Network Shell (NSH) prompt in a BSA environment configured to use an NSH Proxy:
SSO Error: No. authentication profile has been successfully loaded. Single Sign-On connections require a valid authentication profile. Error in Initializing RBAC User and Role (SSO Proxy), errno = 0 (No error) Network Shell can be used for local access
No authentication profile configured in the "secure" file or the file is not accessible by the OS user running invoking the network shell.
This error indicates that NSH does not know what Authentication Profile to use. There are two ways to set this:
Setting the Authentication Profile in the secure file
In the secure file (C:\Windows\rsc\secure or /etc/rsc/secure) on the NSH client system look for the default line:
default:port=4750:protocol=5:tls_mode=encryption_only:appserver_protocol=ssoproxy:Change this to
default:port=4750:protocol=5:tls_mode=encryption_only:appserver_protocol=ssoproxy:auth_profile=MyProfileFor more information about the secure file, review the product documentation.
After making this change in the secure file and getting a SSO token with blcred, start the NSH client.
Setting the Authentication Profile as an environment variableAlternatively the Authentication Profile name can be set as an environment variable.
After setting the variable and getting a SSO token with blcred, start the NSH client.