Spotfire cobranding allows administrators to customize the default login page for the Spotfire Server web interface by creating and deploying a custom login page. However, this customization applies only to the web UI and is not supported in the Spotfire Analyst client.

Since this feature is not currently available for the Analyst client, the article outlines an alternative approach: enabling browser-based login using OAuth2 to support custom login flows and provide a consistent user experience across both Web Player and Analyst.

Since custom login UI is not currently supported in the Spotfire Analyst client, an alternative approach is to enable browser-based login using OAuth2. This allows the Analyst client to redirect users to a browser-based login flow, enabling compatibility with custom login pages.

The Spotfire Analyst client supports OAuth2, and this behavior can be enforced by disabling basic authentication through the Spotfire Server configuration.

Follow these steps to configure it:

Set the following properties:

security.basic.basic-disabled=true
security.oauth2.server.password-grant.enabled=false

1. Export the current Spotfire Server configuration:

config export-config -f

2. Apply the required property by running:

config set-config-prop --name="security.basic.basic-disabled" --value="true"

3 . Import the updated configuration with a label:

config import-config -c "DisableBasicAuth"

Restart the Spotfire Server for the changes to take effect.

This setup will ensure that the Analyst client uses OAuth2 login via a browser, aligning the login experience with the one used in Web Player.

The custom login page configured through Spotfire cobranding is supported only for the web interface (Web Player). When applied to the Analyst client, the custom login UI does not appear, which may result in login failures. Users may expect the same customized login UI to appear in the Analyst client as it does in the Web Player, but this is not currently supported.