Login page changes

The topic describes the changes made to the login page and the impact on the old login page after upgrading to the latest release

In release 9.5.1 and earlier releases, separate URLs were used to access the mobile and desktop versions of the application. With release 9.5.2, a single URL can be used to access both the desktop and mobile versions of the application. A single JSP serves the UI developed using AngularJS. However, the earlier URLs for both desktop and mobile versions are retained in the latest release to support backward compatibility.
Note: From release 9.5.2 onwards, you can access the application across desktop, tablet and mobile devices using a single URL format: http://<host>:<port>/<context>/store/login.do? and should not use http://<host>:<port>/<context>/store/mobile/login.do? to access the mobile version of the application, as mobile login URL is deprecated and will be removed in the next release.

The new login JSP detects the user-agent to determine the appropriate home page to be loaded and does not depend on the login page URL.

Existing feature for landingpage=customerservice (URL request parameter) remains unaffected and it is used to load the home page developed using AngularJS. To load the home page developed using Angular JS, there is no determination of desktop or mobile through user-agent.

Additionally, the following URL request parameters are supported, for pages developed using Dojo framework:
  • landingpage=orderfulfillment for loading the desktop home page
  • landingpage=orderfulfillmentmobile for loading the mobile home page
The URL request parameter landingpage takes precedence over the user-agent in the determination of page to be loaded.

Upgrade impact on earlier customizations

When you upgrade to the new release 9.5.2, you will notice the following changes:
  • If the you have customized the login page and placed it in the <runtime>extensions/wsc/webpages/<path_for_jsp>/ folder and overridden the entries in the strut XMLs, then upon upgrading to the latest version of the application, you will see the old customized login page only. Therefore, to get the new login page, you must override the new login JSP file (<runtime>/repository/eardata/wsc/war/ngstore/jsps/store-login.jsp) and place it in the <runtime>extensions/wsc/webpages/<path_for_jsp>/ folder and update the previously overridden struts XML.
  • If you have followed a different approach than overriding the struts XML and do not see the new login page after upgrading, then you must redo the customization. If you see the new login page after upgrading but want to retain the old customized login page, then you must redo the customization.
  • The following strut entries have been updated for the new login JSP file:
    • Action login , logout, and desktop/redirect in store_core_struts.xml
    • Action login , logout, redirect in store_mobile_struts.xml