Challenge Overview
Overview
Client of this challenge is looking to revamp their current desktop application into a web application, as a part of this process - we are looking for the topcoder developer community’s help in developing the new, refreshing and modern web based application that will help Site Managers, Operators, Business Analysts and Admins with the ability:
- To view the list of meetings that were conducted/attended
- To view list of action items
- To view the LO/TO (lockout/tagout) of the assets
Challenge Requirements
In this challenge you have to update the authentication and authorization implementation in the winning submission of the Integration Challege.
Gitlab Access
Please check the forum.
Authentication & Authorization Requirements
Introduce a Login Screen for the app and the user has to be authorized for accessing any pages. A valid User ID from the DB is required for accessing the pages. The service implementation can do a mock approach where the password check logic can be done against a hard-coded password. All API calls should have come from an authorized session. If the API call is from an unauthorized session then the user should be redirected to the Login page. Please refer the swagger file for how the auth method is defined.
Please note - Technology to be implemented here is Spring Security 5.x
Technology
Client of this challenge is looking to revamp their current desktop application into a web application, as a part of this process - we are looking for the topcoder developer community’s help in developing the new, refreshing and modern web based application that will help Site Managers, Operators, Business Analysts and Admins with the ability:
- To view the list of meetings that were conducted/attended
- To view list of action items
- To view the LO/TO (lockout/tagout) of the assets
Challenge Requirements
In this challenge you have to update the authentication and authorization implementation in the winning submission of the Integration Challege.
Gitlab Access
Please check the forum.
Authentication & Authorization Requirements
Introduce a Login Screen for the app and the user has to be authorized for accessing any pages. A valid User ID from the DB is required for accessing the pages. The service implementation can do a mock approach where the password check logic can be done against a hard-coded password. All API calls should have come from an authorized session. If the API call is from an unauthorized session then the user should be redirected to the Login page. Please refer the swagger file for how the auth method is defined.
Please note - Technology to be implemented here is Spring Security 5.x
Technology
- Java 8
- Spring REST
- Hibernate
- Spring MVC
- JSON
- SQL Server (v13.0.4451.0)
- Spring Framework 5.x
- Spring Boot 1.5.x
- Log4j
- Angular 5.x
- Bootstrap 4.x