Projects:Login Page Clean Up/Specs
There is not any specific functional requirements, the main goal is to keep the Login page working as usual, but without some parts of the code which are no longer needed.
There are several things to consider on the log-in part:
- Old code. For example, currently it is still possible to see the old 2.50 log-in page. This code should be removed.
- The log-in page is divided in three framesets. They will be removed and we will display directly the log-in content without using frames.
- Remove the Home servlet: this servlet was used for initial page in 2.50 right side, it shouldn't be accessible anymore, so it will be deleted together with all related files.
- Remove elements of Vertical Menu servlet: this servlet was used to render the vertical menu in Openbravo 2.50. It will not be completely removed as it is still being referenced within some manual windows (it is placed hidden in manual report and process using old 2.50 technology) but some of its elements can be removed safely (js utility functions, mappings images and styles) as they will not be used anymore.
- Unify the CSS code. The same applies for the CSS styles, currently the page is taking the styles from three different CSS files. Therefore, the required CSS styles will be collected and unified in a single file.
- Once the log-in is performed, a redirect is done to the Menu servlet. Among other things, this servlet is calculating the value of the Startpage of the user preference. Such redirection can be avoided by calculating this preference on the LoginHandler itself.
- Openbravo can be displayed inside an HTML iframe. Once this project is finished we must ensure that this keeps working fine. Some issues related with this topic are: 12479 and 31758.
- Openbravo allows to log-in by using a Google Account. This must keep working also.
During the log-out process, a redirect is done to the Log.html before redirecting to the main log-in page.
That redirection will be removed, but still a redirection to the base URL will be done. This is because after this redirection the final logout actions are performed by the AuthenticationManager. Therefore, this will be maintained in order to ensure backwards compatibility.
After applying this change we must ensure that when a session is no longer active the redirect is working fine under some circumstances:
- After an alert ping
- After opening an standard window
- After opening a manual window, i.e., old Report and Process windows.
- After executing a process from a pop-up