Unauthorized Token has been detected by the System. Please signon with your Userid and Password

Fix:

Please follow the document E-PORTAL: "Unauthorized Token has been detected by the System. Please signon with your Userid and Password" when clicking on pagelet links after upgrade to PT 8.56 (Doc ID 2423420.1)

Delete/empty all the hardcoded URIs from all Node definition under the Portal page and retest the functionality.

         Note there is no real Pcode or standalone application setup need to set these URIs, except the case one             wants to set a portal cluster and/or the developer wanted to fix/hardcode the link PCode generation                   towards a single site.

         However the same coding effect can be achieved in PCode without setting the URI's in such standalone               (non clustered) PS database implementation

Cause of the issue:

New security of PT 8.56 will not allow the site to be switched if this is not part of a portal cluster due to the new PT 8.56 node CheckToken being not validated by such site switch.

Setting the URI's for nodes definitions in such non clustered implementation is not expected.

Oppositely, the URIs are expected to be populated in a clustered PS setup, but in such the new node check token value is expected to be set for all the Default local nodes in the cluster

As far the URI for CRM node is pointed (hardcoded) to the Internet site URI, the PeopleCode Generate: PortalURL and ContentURL PCode functions used in the custom pagelet links are always pointed at run-time to the external site.

All this as far the first place that Pcode looks for at runtime, is to the node URI being set or not, and for a standalone PS app these URIs are not expected to be set..

As far here is not a about a portal cluster (PIH <> CRM) but just a standalone/single PS CRM application (with two sites)  there is no real need to set the node URI!

However, be aware that when using the new ACM templates for setting the IB, could pre-populate the node / portal and content URI's with some, values and this is not expected by the portal and security code if you do not really implement a Portal cluster.