Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-21028

'Enable SSO to M2' setting doesn't work when turned on in the configuration template

    Details

    • Type: Testing Defect
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: CFA 2022R3
    • Fix Version/s: None
    • Component/s: Mobile2
    • Labels:
      None

      Description

      'Enable SSO' to M2 setting doesn't work when turned on in the configuration template. When logged as store level or above store through SSO, users are directed to MXC splash page instead of Mobile2 splash page.

      Environment: CFA Staging
      Stores: 01919 (matt.listi), 02693 and 01171 (bill.digges)

       

      Additional detail: 

      Template created in staging :Mobile2

      Stores - 01919,02693,01171 are added to the Zone associated to the template -->Zone type: InFORM Pilots   Zone: Mobile2 Pilot 

       

      Steps to recreate

      1)load m.informstaging.cfahome.com/m2 page 

      2) User is prompted via SSO to login 

      3) login as matt.listi /CrfMBFtVCzcz1

      Expected

      User should land on the Splash page that has the M2 appended , like this https://m.informstaging.cfahome.com/m2/SplashLandingPage

       

      Actual:

      Login via SSO is not landing on the M2 page as we would expect in a production scenario 

      HOWEVER, once SSO connection is made and user is authenticated and token is created locally and time out has not occured, if the page is closed and url is opened again  – m.informstaging.cfahome.com/m2. The user lands on the M2 splash. However, at this point I am seeing ALL pages in MXC are the M2 pages.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                stacy.privalova Stacy Privalova
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.