SSO Url Endpoint Changes
Martin Walzak avatar
Written by Martin Walzak
Updated over a week ago

We want to inform you of an important update within our system that may require your attention.

Our authentication and service endpoint is transitioning.

This modification is part of our ongoing efforts to enhance our infrastructure and is internal to LawVu.

This update impacts SSO (Single Sign-On) redirect URLs and potentially your firewall whitelisting. If your organisation utilises SSO, please ensure that the appropriate teams are aware of this change and update the SSO configuration accordingly.

We appreciate your cooperation and are here to assist with any questions or concerns.

No further changes to any other SSO settings are required.


Timeframes

This change can be made anytime since both URLs will remain active until the old is decommissioned.


Affected regions

This modification applies exclusively to our clients in the APAC region, whose data is located in Australia.

If your configuration already reflects the region (api-us.lawvu.com or api-fra.lawvu.com) then no changes are required.


Firewall changes

If your organisation uses an on-prem custom SSO solution or an on-prem ADFS server, changes to the perimeter firewall might also be required if domain whitelisting is in place.

Furthermore, if your organisation uses host or subdomain (api.lawvu.com) whitelisting instead of a second-level domain (lawvu.com) whitelisting, then whitelisting must be applied and the new api-aus.lawvu.com included. 


Azure AD Enterprise app changes

Please update the ReplyURL accordingly.

The changes only apply to the hostname part of the domain. Please retain the remaining part of this URL and the identifier unchanged.


OKTA app Changes

Please update your Base URL accordingly.

The changes only apply to the hostname part of the domain. Please retain the remaining part of this URL and the identifier unchanged.


Reporting a problem

Before you report a problem, can you please check the provided guides and help articles? If the issue continues, then please reach out to our support team.

Did this answer your question?