Shop

Your Notifications (0)

There are currently no notifications. You're all set!

Demos Trials
Knowledge Base
ChemDraw and ChemOffice+ Products Signals Notebook E-Notebook and ChemBioOffice Enterprise Spotfire and Signals Spotfire Products Columbus Signals Image Artist
Downloads
Downloads
Community
Support Forums Ideas Portal Product Basics
About Support
Legal Resources Support and Maintenance Plans Product Life Cycle Support News
Contact Support

Unable to login to Spotfire Analyst 11.X onwards due to new usage of the Public Address URL setting

Rich Talbot
  • Updated
Date Posted:
Product: TIBCO Spotfire®

 

Problem:

A user is not able to login to Spotfire Analyst 11.X onwards and some portion of the below error data is reported.

 
Error message: Cannot log in to server.

AuthenticationException at:
Could not authenticate with server to get tokens (no response error). (HRESULT: 80131501)

Stack Trace:

WebException at System:
Unable to connect to the remote server (HRESULT: 80131509)

Stack Trace:
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Spotfire.Dxp.Framework.Login.OAuth2AuthenticationFlow.<>c__DisplayClass19_0.<TryGetTokensUsingUsernamePassword>g__RequestAction|0(HttpWebRequest tokenRequest)
at Spotfire.Dxp.Framework.Login.OAuth2AuthenticationFlow.<>c__DisplayClass27_0.<TryExecuteTokenRequest>b__0()
at Spotfire.Dxp.Services.Http.SpotfireRequest.ExecuteNonSpotfireServerRequestWithRetry(Boolean allowRetryToCauseDuplicateRequests, Func`1 requestCreator, Int32 maxNoOfRetry, Nullable`1 retryDelay, Action checkCancel)
at Spotfire.Dxp.Framework.Login.OAuth2AuthenticationFlow.TryExecuteTokenRequest(Action`1 requestAction, Boolean getRefreshToken, Boolean isPasswordRequest, String& authToken, String& refreshToken, String& scope, Exception& error)


SocketException at System:
No connection could be made because the target machine actively refused it X.X.X.X:X (HRESULT: 80004005)

Stack Trace:
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
 
Solution:

There has been a product design change for Spotfire Analyst 11.X upwards. Whenever any user has upgraded to 11.0 or onward, there is a possibility that the Public Address URL configuration setting and the server name / URL provided during login might differ. Login requires that these values must match. 

Check the Public Address URL setting from the Spotfire Config Tool's Configuration tab, or use any methods described by this article:

How to check the Public Address URL configured on TIBCO Spotfire Server using a Troubleshooting bundle

 

Resolution 1: Update the Public Address URL configuration setting.

To update the Public Address URL setting you may do so from the Spotfire Config Tool. Alternatively, you can do so via command line:

  1. Login to Spotfire Server.
    2. Open a command prompt in admin mode.
  2. Run the following command.

cd "C:\tibco\tss\<version>\tomcat\spotfire-bin\"
config set-public-address -u="Spotfire-server URL" -t password

  • -u specifies the Spotfire server URL in the form of http(s)://host-name:port
  • -t specifies the password of Spotfire Server Configuration Tool.
  • Modify the path of Spotfire installation folder to match your site.
  1. Restart Spotfire Server service for configuration to take effect.
  2. Restart Spotfire Analyst and re-try login.

Resolution 2: In the login dialog use the Public Address URL setting or its server IP address.

If the Public Address URL contains your Spotfire server's Domain Name and you are using the IP Address of that Domain Name, then try adding the IP Address and Domain Name in your Windows hosts file located at C:\Windows\System32\drivers\etc.

Since Spotfire Analyst does not know the IP of the host specified, it intends to search in the hosts file of Windows. If there is no entry for the respective Host name and IP, there is a probability that an error displayed above will be thrown. Once we add the entry for respective Host Name and its IP address, the Analyst is able to get the IP of the Host Name for which it sends request for bearer token generation and successfully sends a request to the token endpoint URL.

For example, if your Public Address URL has http://adityavm01.apacanalytics.lab/
and you specify http://10.97.111.115 as your Spotfire Analyst URL, then add the IP Address and respective Domain Name in your hosts file, as shown below, and also as described in this article: https://www.liquidweb.com/kb/edit-host-file-windows-10/

User-added image

Appendix:

Explanation of new design behavior: The below Dev Tools screenshot is taken from a system where:

Spotfire Server Host name = http://adityavm01.apacanalytics.lab:90

Spotfire Server IP address = http://10.97.111.115:90

User-added image

The above example demonstrates that Spotfire extracts and uses the token endpoint URL from the Response header of the client login request. If the Public Address is set to  http://adityavm01.apacanalytics.lab:80 and actual server address is  http://adityavm01.apacanalytics.lab:90, then the Analyst client would send a request to a wrong token endpoint URL.
 

 

Related articles