If you reconfigure the relying party with SAML 2.0, it does not require future certificate exchanges that may interrupt connectivity when certificates expire (yours or ours). We offer configurations with Google, Azure, and other SAML based Identity Providers. If your relying party is not migrated to SAML 2.0, this certificate update process will need to take place again next year when the certificate is updated again. If you would like to migrate to a SAML 2.0 relying party, please see instructions at https://community.brightlysoftware.com/s/article/SSO-AD-FS-Moving-from-WS-Fed-to-SAML-2-0-Relying-Party-CTAU
You can also contact the Technology support team directly at firstname.lastname@example.org to schedule a working session for help with migration to SAML 2.0.
Posted Jul 13, 2023 - 13:34 EDT
This incident affected: IT Asset Management (Help Desk, Incident, Insight, Mobile Device Management), Work and Asset Management (MaintenanceDirect, PMDirect, CapitalForecastDirect, SchoolDude WorkCenter, InventoryDirect), Energy Management (UtilityDirect), and Event Management (FSDirect, TripDirect).