SAML Login Issues

Incident Report for ThreatLocker

Resolved

This is now resolved

Posted Jun 22, 2026 - 11:56 UTC

Monitoring

URL validation was added to the SAML integration which affected some customers that were using legacy URL configuration.

If you cannot log in using SAML, please enter a LiveChat for assistance, or you can adjust your Assertation URL.

Legacy URLs may contain a double forward slash after threatlocker.com - examples below.
https://betaportalapi.X.threatlocker.com//portalApi/AuthenticationSAML/AssertionConsumerService

To fix, this needs to be changed to a single forward slash:
https://betaportalapi.X.threatlocker.com/portalApi/AuthenticationSAML/AssertionConsumerService

**Please note that X is your Instance and should not be changed from the current value (B, C, D, F, G, H etc)

Posted Jun 19, 2026 - 13:05 UTC

Identified

We are aware of SAML login issues affecting some customers. If you experience any issues with SAML login please come into a LiveChat and we can assist in login. We have identified the issue and are currently working to resolve.

Posted Jun 19, 2026 - 12:23 UTC

This incident affected: Portal (Portal [Instance A]).