20220412 - PSMS Release

Owned by Mark Blair (Unlicensed)
Last updated: Apr 12, 2022
1 min read

Summary:
Migration to .NET 6

Ticket:
https://bigdigit.atlassian.net/browse/PSMS-160

Detail:
.NET 6 ecosystem offers:

  • Simplified development

  • Better performance

  • Improved Security

Summary:
Azure B2C Ready - New Sign-In process

Ticket:
https://bigdigit.atlassian.net/browse/SSO-85

Detail:
PSMS now supports the new Sign-In process using “Azure AD B2C when we complete the user migration to Azure B2C.

Migration to Azure B2C will be done in phases.

Summary:
Azure B2C Ready - Support new application switcher

Ticket:
https://bigdigit.atlassian.net/browse/PSMS-176

Detail:
Users will have the ability to switch between applications from the User Account menu when we complete the user migration to Azure B2C.

Summary:
Changes to Application Infrastructure for Azure B2C

Ticket:
https://bigdigit.atlassian.net/browse/PSMS-184

Detail:
PSMS is now ready to be used with Azure B2C. We will be migrating to Azure B2C in phases.

Summary:
Application Insights now filtering expected 404 errors

Ticket:
https://bigdigit.atlassian.net/browse/PSMS-170

Detail:
Application Insights is now easier to use and we filter out all expected 404 errors.

Summary:
Update ingress controller settings to the latest scheme

Ticket:
https://bigdigit.atlassian.net/browse/PSMS-182

Detail:
Ingress controller settings updated to latest scheme.

Summary:
Handle interrupted Azure B2C login process

Ticket:
https://bigdigit.atlassian.net/browse/PSMS-188

Detail:
Fix to handle Azure B2C login process when it is interrupted by the user.
For example, during the login process, the user can click on the Indigina logo to go to Apps selection page. This fix can handle these situations so the user can still login after the initial login process was interrupted.

Summary:
Migrate Public API Tokens to use the TokenManager service

Ticket:
https://bigdigit.atlassian.net/browse/PSMS-174

Detail:
Clients send HTTP requests to a Public API with a “Token“ query parameter. The Public API tries resolve the token via the Token Manager. If the token is valid, the Token Manager returns Access Token information and the Public API allows the request.

Â