Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Simplified development

  • Better performance

  • Improved Security

...

Summary:
Support for application switcher when we move to Azure B2C Ready - New Sign-In process

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyPSMSSSO-17685

Detail:
When we move 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 , users will have the ability to switch between applications from the User Account menuwill be done in phases.

...

Summary:
Azure B2C Ready - Support new Sign-In process when we move to Azure B2Capplication switcher

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keySSOPSMS-85176

Detail:
PSMS supports new Sign-In process using “Azure AD 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 to support for Azure B2C

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyPSMS-184

...

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:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyPSMS-182

Detail:
Ingress controller settings updated to latest scheme.

...

Summary:
Handle interrupted Azure B2C login process

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyPSMS-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:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyPSMS-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.

...