How to create a new client secret for Azure application 'B2C-FinancialsLive-Auth'

Approximately every 2 years we need to update the client secret on the Azure application 'B2C-FinancialsLive-Auth' otherwise users access to the application will stop working.

A freshservice process has been put in place to generate a new freshservice ticket about a month before the current secret is due to expire, which expires on the 7/4/2027

To update the secret you will need to do the following:-

First you will need to give yourself 'Application Administrator' PIM role - My roles - Microsoft Entra admin center

One PIM role has been assigned browse to - App registrations - Microsoft Azure

Locate and click on the application 'B2C-FinancialsLive-Auth', this should be located under all applications, or under owned applications

After clicking on the application you should see a page similar to below, click on what i have highlighted in the screenshot and it will then take you to the page to add a new secret.

You should then be take to the following:-

Click on '+ New client secret'

A new blade will open, complete the details as follows:-

Description - 'B2C-FinancialsLive-Auth-Secret'

Expires - 730 days (24 months)

Then click on 'Add' at the bottom of the page

This will create a new secret, and you should then see 2 secrets, the current secret which will be due to expire soon, and the new secret you just created.

As you can see above we have the current secret which is due to expire on 7/4/2027, and the new secret i have created as part of creating this solution article which expires on 14/4/27 , which i will delete shortly.

Record the new value and secret ID in Bitwarden which is saved in the entry for 'B2C-FinancialsLive-Auth-Secret'

You will need to supply Civica support with the value and the secret ID, make sure you make a note of the value as once you navigate away from this page you will not see the value again as it will be **** out

The new secret would need to be made active at an agreed time and date in conjunction with Civica support as they need to add this new secret on there systems at the same time we make the change on our Azure portal.

When a time and date has been agreed to change the client secret, delete the old secret which then forces the new secret to become the current and active secret. Civica will do similar on their systems.

There may be a brief interuption to access to Civica Financials while the new secret is implemented. This is the link to login to Civica Financials - https://lanliv.financials.cf-civica.com/Transformation/Login.aspx

I got an error when trying to access this link for about a minutes when the new secret was applied, i was able to login again after about a minute.