...
Simplified development
Better performance
Improved Security
...
Summary:
Support new Azure B2C Ready - New Sign-In process for Azure B2C migration
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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 for Azure B2C migration
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
When we move to Azure B2C, users 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
...
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 | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Ingress controller settings updated to latest scheme.
...
Summary:
Handle interrupted Azure B2C login process
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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 | ||||||
|---|---|---|---|---|---|---|
|
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.
...