Ping SSO SAML Taking Users to Classic on Login (16.1.3+)
search cancel

Ping SSO SAML Taking Users to Classic on Login (16.1.3+)

book

Article ID: 274527

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

On Ping SSO and recently upgraded to Clarity 16.1.3. After the upgrade the user is taken to Classic /niku/nu after SAML authentication regardless of where the URL is taking them (usually a MUX URL or a deeplink). Once the user is logged in, they are able to go directly to MUX or deeplinks.

Our Sign On URL is set to the below, as required:

https://SERVERNAME/idp/startSSO.ping?PartnerSpId=https%3A%2F%2FSERVERNAME%2Fniku%2Fnu%23action%3Aunion.samlMetadata&TargetResource=

This used to work on 16.1.1

Environment

Release : 16.1.3

Resolution

Starting 16.1.3, &RelayState= is getting appended, which causes the problem as Ping SSO does not accept this syntax.

  1. Update the SignOnURL with URL like this:
    https://SERVERNAME/idp/startSSO.ping?PartnerSpId=https%3A%2F%2FSERVERNAME%2Fniku%2Fnu%23action%3Aunion.samlMetadata&TargetResource=https%253A%252F%252FSERVERNAME%252Fpm%252F%2523%252F
  2. Restart the services