In ‘seamless' navigation, where you navigate from classic to the new UI. We are making a GET /ppm/rest/v1/auth/login?_cb=<timestamp> call to determine whether there is an active session. If yes, then we make the UserContext call to retrieve the logged in user’s data. We are able to do this because you logged into classic first, and classic is setting a browser cookie, which gets passed automatically (transparently) in the new tab for the new UI. This is working as designed in our staging environments. The result of the GET login determines where we allow direct access to the requested url, or show the user the login page.
The GET login call will always return a 200 response, and the payload determines the next action in the new UI.
The fact that the classic logs are showing a null pointer exception indicates that the GET login call is expecting a value from the client which is NOT being passed automatically. To debug this further, we need to see the cookies that are passed in the GET login call from the customer. I suspect that the "sessionId" cookie might be set by classic, but the customer’s environment may be interfering (changing, or removing) cookies and causing the problem.
Logged into classic first, http://server:8080/niku/nu#action:npt.overview then changed the url to server:8080/pm to simulate seamlessly navigating to the new UI. Notice the Cookie contains the sessionId parameter and value.
Please send the GET login call with complete headers, showing the Cookie value.
Regards
Suman Pramanik