Hi Vinoth - the issue was that you changed the production level of your system from 4 to 1, which changes the DB that sso externally authenticate against. This change doesn't go into effect until after a restart, which is why you started seeing issues after the node change - it was the reboot rather than the node change itself. I set your system back to level 4 and you should be good to log in again now.
Hi Vinoth - Changing the browser type to not see PTC:Unauthenticated rules will break the /sso login screen, yes. I recommend either building an Unauthenticated access group that works for both MCC and PTC rules or creating a non-sso operator to use to log into your app.
Hi @MattE - I am going with the first option that you have recommended. In my Unauthenticated Access Group I have added the "PTC-Authentication" as one of the Production Rulesets in the Run Time Configuration under the Advanced tab.
By doing this I think my Unauthenticated access group will work for both MCC and PTC rules. Please correct me if I am wrong.
Hi Vinoth - I think you might need the PegaPCDIntegration ruleset as well as PTC-Authentication. Or you could just add the TrialAuthentication:01.01.01 application to your app stack and that would do it.
It's easy to test. Make sure you stay logged in just in case it breaks and open an incognito or private session and verify you can see the login screen and login.