Use ASPNET framework for user management.

The following changes are required:

1. Backoffice user maintenance will use aspnet security
2. Backoffice login
3. POS login
4. Reporter Login
5. POS authorization
6. Changes to replication

The following design has been agreed:

1. In order to secure existing BackOffice users, we need to have a single sign-on for all BackOffice functionality. Backoffice modules are PAY, HRM, INV, PUR, POS, FMS, ESS. This means we combine ESS, POS and FMS web applications into 1 web application named: Link Backoffice (LBO) 
   1. Existing roles will be prefixed with existing application code.
   2. Users imported from ESS, POS, and FMS will be mapped to respective roles.
   3. Users security will be merged. If you have access to "user maintenance" in ESS and not in POS, then you will have access in LBO.
2. When a user is created in BackOffice, we have a two-stage save process:
   1. Pass ASPNET user details to dot net component
   2. Save Non-ASPNET  details into SY_USER which will be renamed to LT_SAA_User
3. Password recovery and encryption will be handled by ASPNET. 
4. Add reset password option in BackOffice  
5. Create a user in BackOffice by passing username, password, and email address. For existing user, you have the option to reset the password (password will be emailed to the user)
6. Change password. This will require the old password.
7. BackOffice role menu access structure will remain unchanged.

The ASPNET framework allows us to maintain user security requirements based on Microsoft best practices without having to worry about the design considerations. As a result, we are considering making the following changes:

1. Merging ESS, POS, FMS, RM, HEL into one application framework so users have a single sign-on
2. Converting Backoffice user management into ASPNet framework using 1. above
3. Simplifying licensing by merging common applications
4. Checking "Named users" instead of "Concurrent users"
5. Changing license check at "form level" instead of "user maintenance"

Version 9.5 is expected to have significant changes with the core aim being Simplification, Standardising and Ease of use.

1. The following changes were made(Include Database object names, Program classes and any other relevant information):|

1. Added backoffice login validation to use ASPNET user accounts
2. Removed "Password change" and "Force Password change" options from Backoffice
3. Changed Backoffice forms to accommodate user maintenance
4. User Menu structure has not changed in backoffice, so users need to be added from the ASPNET user pool in Backoffice
5. User maintenance is all handled in the WEB framework

Test Update

1. Added backoffice login validation to use ASPNET user accounts - Logged case 9517 and 9158 
2. Removed "Password change" and "Force Password change" options from Backoffice - Pass
3. Changed Backoffice forms to accommodate user maintenance
4. User Menu structure has not changed in backoffice, so users need to be added from the ASPNET user pool in Backoffice
5. User maintenance is all handled in the WEB framework

Thanks
Rashna

Hi Sanjay, 

Documentation on the case has been completed.

Document update under

• Systems Manager -- Master Security -- User Login.

Thanks
Rashna