In TIBCO Spotfire Server, OpenID Connect with Okta works for port 443 but fails if other ports (such as 8443) are used.

In TIBCO Spotfire Server, OpenID Connect with Okta works for port 443 but fails if other ports (such as 8443) are used.

book

Article ID: KB0075339

calendar_today

Updated On:

Products Versions
Spotfire Server All versions

Description

When setting up OpenID Connect with Okta on TIBCO Spotfire Server, it works correctly for the default port 443 but fails when non-default ports (such as 8443) are used.

Issue/Introduction

When setting up OpenID Connect with Okta on TIBCO Spotfire Server, it works correctly for port 443 but fails when other ports (such as 8443) are used. This can be due to not having specified the port for the address in all places in the configuration.

Resolution

For port 443 you do not have to set a port in the public address and Redirect URL. The port 443 is default for HTTPS. When using port 8443 (or any other non-default port) you need to explicitly enter the port in all places in the configuration in the Okta portal as well as in Spotfire configuration for OpenID connect.

Thus, make sure the port is specified in the following places.

(1) Okta portal:

  • For the login redirect URl, specify the address with the 8443 port included.
(2) In TIBCO Spotfire Server Configuration tool:
  • Public Address tab - Enable public address with the 8443 port defined and restart Spotfire Server (or run command set-public-address).
  • OpenID tab - Enable OpenID connect with the 8443 port defined for the Return endpoint address

Additional Information

How to configure OpenID connect authentication with Okta on the TIBCO Spotfire Server:  Configuring OpenID Connect:  Manually editing the server configuration in the configuration tool:  set-public-address: