Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Summary:
Azure B2C Ready - New Sign-In process

Ticket:
SSO-83 - Getting issue details... STATUS

Detail:
Notification System 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:
Notification System updated to use Angular 13

Ticket:
NOT-333 - Getting issue details... STATUS

Detail:
Notification System now uses Angular 13 providing performance improvements and support for modern web development standards.


Summary:
SendGrid webhook keys masked by default

Ticket:
NOT-337 - Getting issue details... STATUS

Detail:
When working on the “Partner Maintenance” page it no longer shows all the SendGrid webhook keys in plain text by default. Instead these are masked by default with the option to display it in plain text.


Summary:
Update ingress controller settings to the latest scheme

Ticket:
NOT-346 - Getting issue details... STATUS

Detail:
Ingress controller settings updated to latest scheme.


Summary:
Handle interrupted Azure B2C login process

Ticket:
NOT-349 - Getting issue details... STATUS

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:
Info component to assist users with sending notifications on the front end

Ticket:
NOT-339 - Getting issue details... STATUS

Detail:
Info text now appears at the top of the “Send Notification” page describing the required format and process for pasting email addresses.


Summary:
Migrate Public API Tokens to use the TokenManager service

Ticket:
NOT-327 - Getting issue details... STATUS

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.


Summary:
Improved styling of front end components

Ticket:
NOT-341 - Getting issue details... STATUS

NOT-335 - Getting issue details... STATUS

NOT-356 - Getting issue details... STATUS

Detail:
Improved styling of the following front end components:

  • Drop Down

  • Multi-Select

  • “Edit” buttons

  • “Add new” buttons


  • No labels