OWB not able to connect with SSO (On Premise)
search cancel

OWB not able to connect with SSO (On Premise)

book

Article ID: 279168

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

You have just set up OWB with SAML SSO and not able to connect with OWB, getting an error:

The stream version from the server is not the same as the client's stream version

When SSO is disabled, OWB is working again

Resolution

OWB Client does not fully support SSO in On Premise setups

The recommended configuration is to add a Non SSO app to Clarity in combination with working LDAP

Note: this will only work if the SAML SSO credentials are the same for Clarity (used in LDAP)

  1. Connect to Clarity app server, ensure you have enough RAM and find an open port
  2. Run the command service clone app
  3. This creates a new service app2.
  4. Connect to properties.xml or CSA and set up the app2 service to run on an open port you determined in step 1. Make sure the JVM memory is appropriate
  5. Add the Non SSO app in Scheduler URL as follows:
    http://example.com:8080
  1. Make sure the Non SSO app is not enabled for SSO, and do not add it to load balancer
  2. Save, start and deploy the new service
  3. Make sure you able to connect directly to this new URL from the server with your LDAP credentials
  4. Now connect to OWB when using the Non SSO app URL and port, also the same LDAP user credentials