Request with Basic Authentication fails with "Username not available for authentication" on the BS console.
Article ID: KB0086963
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Description:
Request with Basic Authentication fails with "Username not available for authentication" on the BS console.
Symptoms:
The Swagger UI does not provide the option to provide basic authentication. We cannot provide the username and password to authenticate our-self.
Cause:
No Option to provide credentials in Swagger UI.
Request with Basic Authentication fails with "Username not available for authentication" on the BS console.
Error details follow:
<>@BWEclipseAppNode> 14:03:10.695 ERROR [bwResourceHTTPConnector.qtp-104] c.t.g.pa.action.util.LogUtil - Username not available for authentication.
14:03:10.695 ERROR [bwResourceHTTPConnector.qtp-104] com.tibco.amx.login.failure - Authentication failed.
14:03:10.729 ERROR [bwResourceHTTPConnector.qtp-104] c.t.g.p.a.api.AbstractActionManager - Failed to execute action.
com.tibco.governance.agent.action.security.SecurityException: Authentication failed.
Symptoms:
The Swagger UI does not provide the option to provide basic authentication. We cannot provide the username and password to authenticate our-self.
Cause:
No Option to provide credentials in Swagger UI.
When you launch BW process in Studio, its command is "lrestdoc", which will populate the following for you:
lrestdoc
[Application Name]: LdapConn.application
[Discovery Url]: http://dchauhan-T430:7777/LdapConn.application
[Reverse Proxy Url]: null
When you access the Discovery URL in Swagger, you will see the error.
Issue/Introduction
Request with Basic Authentication fails with "Username not available for authentication" on the BS console.
Resolution
Use a Postman rest client or an external client like SoapUI to access it. Choose Basic Authentication and provide a username and password.
Feedback
Yes
No
Powered by
