Review of Issues in the "Review" and "Completed" lane of the SORMAS Foundation

[markusmann-vg]

Problem Description

Several issues have recently been tagged as "Completed." Before merging them into the main branch, a thorough review is necessary.

https://github.com/orgs/SORMAS-Foundation/projects/7/views/1

Proposed Solution

The review should focus on two key areas:

1. Impact on the Main Branch:

• Evaluate the potential effects these changes will have on the stability, functionality, and performance of the main branch.
• Identify any breaking changes or dependencies that may require further testing.

2. Quality of Pull Requests:

• Ensure that all submitted pull requests are of high quality, adhering to the project's coding standards and contribution guidelines.
• Verify that appropriate testing has been completed, and documentation is up-to-date where applicable.

Checklist:

• Review completed issues for any potential impact on the main branch.
• Validate that all pull requests related to these issues follow the contribution guidelines.
• Confirm that tests have been conducted and documentation updated as needed.
• Identify any additional tasks necessary for a smooth merge into the main branch.

Additional Information

Please make sure to assign reviewers accordingly and provide feedback directly on the related pull requests.

Especially this issue caught my attention:
#12881 => Password reset Merge back to SORMAS main branch

[ ] Is there a feature configuration ?
[ ] Is it hidden, when keycloak is enabled?
[ ] If not, does it redirect the user to the keycloak feature of resetting the password?

...

[daveotengo]

1. Is there a feature configuration ? Yes its done now.

2. If not, does it redirect the user to the keycloak feature of resetting the password? Yes its done now.

[daveotengo]

For authentication Provider keycloak reset password implementation has now been changed from redirect to forgot password to allow for the user enter current, new and confirm password.

Thanks
David Oteng