{"id":7627,"date":"2020-05-14T16:14:04","date_gmt":"2020-05-14T16:14:04","guid":{"rendered":"https:\/\/www.dotcom-monitor.com\/blog\/?p=7627"},"modified":"2026-06-15T15:32:58","modified_gmt":"2026-06-15T15:32:58","slug":"monitoring-applications-that-use-okta-for-user-authentication","status":"publish","type":"post","link":"https:\/\/www.dotcom-monitor.com\/blog\/monitoring-applications-that-use-okta-for-user-authentication\/","title":{"rendered":"Monitoring Applications that use Okta for User Authentication"},"content":{"rendered":"

Okta<\/a>\u00a0is a trusted leader in identity and access management, helping enterprises provide secure access to important tools for employees, partners, suppliers, and customers. With its extensive integration network\u2014connecting to over 6,000 applications\u2014the Okta Identity Cloud makes it simple and secure to access resources from any device. While Okta doesn\u2019t include built-in synthetic monitoring for web applications, it does offer a few helpful reporting tools to keep you informed. Here are some examples:<\/p>\n

Okta Trust Site: <\/b>This site gives you an at-a-glance view of Okta\u2019s system status<\/a>. By logging in with administrator credentials, you can check the availability of the Okta server that hosts your subdomain, ensuring you\u2019re always in the loop.<\/p>\n

On-Premises Agent Health Checks:<\/b> Certain on-premises Okta agents, like the Okta AD Agents, have built-in health monitoring features. Okta keeps a close eye on these agents and sends email alerts to all administrator accounts within minutes if downtime occurs. You can find even more details about AD Agent availability here<\/a>. These tools ensure you can keep tabs on your Okta setup and stay informed without needing synthetic monitoring.<\/p>\n

Monitoring Application Access<\/h2>\n

Monitoring access to applications through Okta has its limitations. Okta reports don\u2019t provide direct notifications for application downtime, and the System Log always shows a successful authentication for applications integrated through SAML or WS-Federation. This happens because, due to asynchronous authentication, the browser will continue to relay a SAML assertion to the service provider, resulting in an HTTP 200 response even if the service itself is down.<\/p>\n

To address these limitations, third-party synthetic monitoring tools can be invaluable. With Dotcom-Monitor, you can:<\/p>\n