govService Release 492: January 11, 2022

govService Platform

Improvements

Following are improvements we have made to existing features:

Forms

• We have added a new class ("fs-hidden") to form fields which have the Hidden setting enabled. This new class allows hidden fields to be targeted within custom styling.
• The Upload field has been updated to use the aria labelled-by technique to associate its label with the field.

• We have increased the speed for searching Integration logs by removing the automatic search which currently occurs after two characters are entered. Searching is now initiated by users clicking Enter, which makes it faster by reducing the number of actions taking place in the background.
• Performance of the Integration logs page has been optimised so that it now loads faster and doesn't crash for sites containing large amounts of data. This optimisation has been done by removing the page numbers previously displayed at the bottom of the Integration Logs tab. Generating the page numbers for sites with large amounts of data was resource intensive and caused significant delay to page loads.

• The MyAccounts tab available on customer records within Service has been optimised to improve performance.

Bug Fixes

• In Forms, validation has been added to prevent processes being imported into the platform when the process name contains a space within the prefix. This prevents bugs that would otherwise be caused by a process containing an invalid space character.
• We have resolved an issue with Civica Estore not returning the same extra data as Civica Paylink if enabled. Civica Estore now returns extra data for the following fields: data_originatorsreference, data_incomemanagementreceiptnumber, data_responsedescription, data_paymentauthorisationcode, data_cardscheme, data_cardtype, data_paymentamount.
• We have fixed an issue with Gov Pay metadata not being passed to the payment provider.

Reminder: LIM Security Update

Granicus will soon be releasing a LIM security update for govService, which will impact a subset of govService customers that use the Inbox functionality with Office 365 as their email provider.

Please have your IT team complete the steps below to determine if you are impacted by this update.

1. Log onto the server that hosts your LIM application
2. In Windows Explorer, search "lim.config"
3. Open the file titled lim.config in Notepad.
4. Check for the following line in the file. If the line is present and identical to the text below, you will be impacted by the update:
   <add key="IMAP.Server" value="outlook.office365.com"/>

If the steps above determine that you will be impacted by the update, please reach out to Granicus Customer Support via support@granicus.com or submit a ticket via our Support site.

Further details about the update are provided below.

What is Granicus releasing for govService?

Microsoft is deprecating their Basic Authentication (Basic Auth) and the end of Basic Auth will impact all govService customers using Office 365 for Inbox. We are building out a new LIM which will authenticate using the OAuth2 protocol, which Microsoft will still support.

Reference here for the full press release from Microsoft.

What should I expect from this update?

This update will include a new authentication interface and enhanced security update. As a customer, if you are impacted (see steps above), you will need to reach out to Granicus Customer Support, who will help you re-authenticate your credentials to ensure that this will not impact your experience with the Inbox functionality.

When will this take effect?

Microsoft has not been explicit in their communication as to when they will disable Basic Auth on Office 365 accounts. Out of caution, we recommend reaching out to Granicus Customer Support as soon as possible if you are impacted and completing the steps for re-authentication before February 1st. Sometime in January, we will be providing impacted customers with a detailed user guide, which will walk through how to re-authenticate and the steps for proper set-up. If you wait to reach out, you risk potential loss of inbox files, all relevant data, and access to your inbox when Microsoft implements the change on their end.