6.0.7-SP1

Release notes - MyChild6 - v6.0.7-SP1

Bug

MST6-810 DataProtection Keys are not loaded properly

Description

The Problem: during the merge project it looks like the DataProtection configuration got changed, when upgrading an existing Windows install, the patient names are all encrypted and you have to add the DataProtection configuration to fix it.

Recommended Resolution: Correct the data protection loaders so that the keys are correctly loaded during startup

MST6-811 LDAP users cannot log in with user-friendly domain

Description

The Problem: When configuring LDAP integration, we have to configure the application to query the AD server directly using the full domain name (IE: ad01.mydomain.com), however, users will typically have a username like myuser@mydomain.com. This is a problem because the code expects you to log in with the same “domain” that is set in the appsettings.json

Recommended Resolution: update the backend logic to check to see if the main parts of the domain name match and then process the request based on that result (IE: user@mydomain.com should be the same as user@ad01.mydomain.com)

MST6-812 Sys-Admin | Alarm Acceptor

Description

It was found our mass alarm acceptor in our system admin page is not working as it should.

I have found a 404 error and a reference error on the index page.

MST6-813 LDAP User roles are not updated

Description

The Problem: When a users group (IE: Role) is changed in LDAP, that change is not reflected in the MyChild Software, so for example, if a user is created with a role of “ClinicalStaff” and then at some point down the road they are placed into a different group (IE: ClinicalAdmin) the role is never updated in MyChild

Recommended Resolution: When a user logs into the system, we should verify that thier role matches whatever LDAP group they are in, if they don’t match (IE: LDAP is different from MyChild), then we should updated the MyChild side to match the LDAP side

MST6-814 LDAP Disabled Accounts Able to login

Description

The Problem: When an account has been disabled in the LDAP Server, the account should NOT be allowed to login to the software anymore, however for some reason the LDAP active flag seems to be being ignored for some reason.

Recommended Resolution: update the login procedure to verify the acount active flag, if the account is not active (IE: disabled) then the login should be denied

MST6-815 MyProfile | Static size

Description

Our MyProfile page will break when a user zooms into the page using the default zoom on the web browser (ctrl + ScrollWheel).

Our navigation menu has an overlay that starts to break and push things around.

All pages attached to the myprofile page need to use percentages for dynamic sizing, this included the text fields as they may overlap with Zoom.