Troubleshooting authenticity problems

Find information to help resolve issues that you might encounter related to authenticity.

table lists possible problems and actions to take to troubleshoot

Problem

Actions to take

The client runtime continually makes requests to the MobileFirst Server and the server responds with the same authentication request.

The WL.Client.addGlobalHeader("Cookie", "name=value") API in JavaScript might cause a product client to enter an authentication loop. The product uses cookies internally to maintain session states between the client and the server. The WL.Client.addGlobalHeader API replaces the entire 'Cookie' header and destroys the session state. Do not use the WL.Client.addGlobalHeader("Cookie", "name=value") API. Instead, use the document.cookie = "name=value" API within the JavaScript logic. The document.cookie API ensures that the cookie is appended to the existing cookie list instead of replacing all existing cookies.

Parent topic: MobileFirst security framework