SC unable to connect to a SSO-enabled Clarity environment

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

It is not possible to log in directly via Schedule Connect to a Clarity that uses SSO (in both Microsoft Project and Open Workbench).

Steps to Reproduce:

1. Log in to an SSO enabled Clarity environment.
2. Create a new user. Under Administration > Organization and Access > Resources, set a known password and enable the checkbox 'Allow Direct Login when SSO is Enabled'.
3. Open a project in Clarity, then open in scheduler (depending on the configuration this will be MSP or OWB).

Actual and Expected Results: Project opens in MSP/OWB.

4. Close MSP or OWB completely.
5. Open MSP or OWB standalone (i.e.: not from Clarity and not using a sched.nikusl file).
6. Open the Schedule Connect dialog to connect to Clarity and click on 'Setup >>'. Previous configuration will be listed.
7. Enter the credentials of the non-SSO user and connect.

Expected Results: Project opens in MSP/OWB.

Actual Results: Project does not open. MSP freezes in the Connecting step, and OWB shows a popup error: 'The stream version from the server is not the same as the client's stream version.'.

Environment

Any SSO-enabled Clarity environment.

Resolution

It is currently not possible to log in to an SSO enabled Clarity environment using Schedule Connect directly.

Workarounds:

1. Open the project from Clarity using the "Open in Scheduler" menu.
2. (On Premise only) While using Schedule Connect, connect to a non-SSO app service directly for the same Clarity environment.