SSO Availability

Remediation of this issue has been validated with several impacted clients.

The root cause of the issue was identified as an incorrect script designed to automate certificate updates. This script incorrectly updated X509 certificates for all SSO configurations, not just a single configuration. This script has been remedied for future use to confirm only a single configuration is updated.

If clients still experience issues with SSO authentication, please submit a support ticket to info@getblueprint.io

A root cause was identified for this issue. When a X509 certificate was updated for an sso configuration, it was incorrectly applied to multiple client's SSO configurations. The remedy has been tested and confirmed with several impacted clients. Impacted clients need to open the SSO configuration inside Blueprint (https://income.getblueprint.io/Account/SSOconfig.aspx) and update the X509 certificate with the value from their system and overwrite the current value. An administrator on the account with username / password authentication will be needed to access this page and make the required update.

Over the weekend authentication certificates were refreshed for Blueprint for their internal SSO configuration. We believe during this update the SSO configuration of clients who have configurated SSO directly with Blueprint were affected and their configuration settings were changed at this same time. This is resulting in SSO authentication errors for users.

Clients with SSO configured have been directly contacted to notify them of this issue.

Clients with username / password access are not impacted. Encompass and API clients are not impacted.

Impacted users should have their IT team re-confirm the SSO configuration settings inside Blueprint by visiting https://income.getblueprint.io/Account/SSOconfig.aspx and confirming the endpoints and certificate match your intended configuration.