Clarity

Expand all | Collapse all

PPM 15.1 New User Experince URL recieves 404 error

  • 1.  PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 17, 2017 10:33 AM

    After installing the needed PMO add-on and activating the 'New User Experience' in the admin settings receiving a 404 error when accessing the URL (https://<server>/pm). Classic UI works fine.

     

    Settings

    Clarity Home : C:\niku\clarity

    Tomcat Home  : C:\niku\tomcat

    New User Experience Directory :  C:\niku\clarity\tomcat-app-deploy\webapps\pm

    Windows Server 2008

     

    Is there some additional configuration needed?



  • 2.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 17, 2017 11:52 AM

    Double check it's enabled

    check the properties file



  • 3.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 17, 2017 11:54 AM

    I only activated the New User Experience. Did not activate the Timesheets.



  • 4.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 17, 2017 12:00 PM

    should be accessible without activating timesheets.

    check the properties file



  • 5.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 17, 2017 12:06 PM

    properties file shows the new user experience as activated

    <war context="pm" name="ppm-ux" enable="true"/>



  • 6.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Broadcom Employee
    Posted Jan 17, 2017 12:12 PM

    Is there an error in your app-ca.log file?  If so, please post it.

     

    Jeanne



  • 7.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 17, 2017 12:33 PM

    No Error but there are some warnings

     

    WARN  2017-01-17 12:28:54,556 [ajp-nio-8009-exec-3] utility.I18nUtilities (clarity:k.shiverdecker.adm@wpafb.af.mil:22765312__A2B3E194-24DE-4BBF-BF88-76ACB1240033:npt.overview) Unable to find gwtconstants/TimeZoneConstants for locale en finding default
    WARN  2017-01-17 12:28:54,665 [ajp-nio-8009-exec-3] utility.I18nUtilities (clarity:k.shiverdecker.adm@wpafb.af.mil:22765312__A2B3E194-24DE-4BBF-BF88-76ACB1240033:npt.overview) Unable to find gwtconstants/DateTimeConstants for locale en_US finding default
    WARN  2017-01-17 12:28:54,665 [ajp-nio-8009-exec-3] utility.I18nUtilities (clarity:k.shiverdecker.adm@wpafb.af.mil:22765312__A2B3E194-24DE-4BBF-BF88-76ACB1240033:npt.overview) Unable to find gwtconstants/DateTimeStringConstants for locale en finding default
    WARN  2017-01-17 12:28:58,268 [ajp-nio-8009-exec-6] caching.SecurityObjectCache (clarity:k.shiverdecker.adm@wpafb.af.mil:22765312__A2B3E194-24DE-4BBF-BF88-76ACB1240033:odata.GetNavigatorMenuBean)  Invalid security object key: BURDENING_MATRIXRECORDPAC



  • 8.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Broadcom Employee
    Posted Jan 17, 2017 12:52 PM

    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 



  • 9.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 18, 2017 06:47 AM

    Here is a screen shot



  • 10.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Broadcom Employee
    Posted Jan 18, 2017 07:07 AM

    I see you have IIS in the middle, can you please bypass the IIS and then check. 



  • 11.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 18, 2017 07:22 AM

    IIS handles our authentication into our apps. We are using SSO and CAC cards. I will have to check with our network guy to see if it can be done.



  • 12.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 18, 2017 09:00 AM

    My admin noticed I wasn't following the pm in the url with a slash. I tried the https://<server>/pm/ and got to https://ippm.proto.devebs.afrl.af.mil/pm/#/login. This was post me authentication via the classic URL. Is there something special you have to do to enable SSO for the new UI?



  • 13.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Broadcom Employee
    Posted Jan 18, 2017 09:26 AM

    Hi Kenneth,

     

    If you come through classis URL you shouldn't get the login page, also in case of SSO, it will authenticate against PPM and yes if you have protected the URl then you may need to allow /PM in your SSO set up 

     

    Regards
    Suman Pramanik



  • 14.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 18, 2017 10:04 AM

    /pm is allowed in our SSO setup. Its like the header variable isn't being recognized. I tried to login with a user name and password and get

    Failed to sign in! Could not connect to login endpoint. 



  • 15.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Broadcom Employee
    Posted Jan 18, 2017 10:09 AM

    Hi Kenneth,

     

    Yes it could be browser setting also, it would be worth logging a case and we can take a look at it.


    Regards

    Suman Pamanik 



  • 16.  Re: PPM 15.1 New User Experince URL recieves 404 error
    Best Answer

    Posted Jan 18, 2017 10:55 AM

    I wasn't a browser setting. Turns out we had two issues. We had the REST API Access disabled in the NSA Application settings and had the ppm/rest/* url mapping missing in the <clarity root>\redirector\conf\uriworkermap.properties file. Only had pm/* mapped, you need both pm/* and ppm/rest/* mapped.

     

    Thanks for getting me pointed in the right direction.



  • 17.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Broadcom Employee
    Posted Jan 18, 2017 11:05 AM

    Thanks Kenneth for providing the information 



  • 18.  Re: PPM 15.1 New User Experince URL recieves 404 error

    Posted Jan 18, 2017 11:06 AM

    Thanks Kenneth for providing the solution. One to add for future troubleshooting