All Systems Operational

AD / LDAP Connector Authentication

Normal

Admin Service

Normal

API Service

Normal

Desktop SSO

Normal

Directory Imports

Normal

Event Broadcaster Service

Normal

MFA

Normal

OneLogin Desktop Service

Normal

OneLogin Portal App

Normal

OneLogin Protect / OneLogin SMS

Normal

OneLogin Workflows

Normal

Portal

Normal

Provisioning Service

Normal

RADIUS Service

Normal

Single Sign-On Service

Normal

SmartFactor

Normal

Virtual LDAP (VLDAP) Service

Normal

AWS CLI

Normal

Trusted IDP

Normal

Smart Hooks

Normal

PKI

Normal

Google Chrome Browser Extension

Normal

PAM Essentials

Normal

Scheduled Maintenance

Schedule

April 25, 2025 5:30PM - April 26, 2025 12:00AM PDT

Components

Admin Service, OneLogin Desktop Service, Portal

Locations

US Operating Region

Description

This is a reminder that we will be performing a migration of the main database to Aurora in the US Shard on April 26, 2025, from 00:30 a.m. to 7:00 a.m. UTC. During this period, the database is scheduled to be in read-only mode from 00:30 a.m. to 4:30 a.m. UTC and the following actions will fail to complete: Any administrative tasks, including: - Creating/Deleting/Updating users - Configuration changes Any API Calls performing Create/Update/Delete operations - NOTE: Customers using custom API authentication should verify that authentication flows do not include REST API Create/Update/Delete calls. - The following OIDC calls are made against the Read-Only database and WILL continue to function: -- POST request with grant_type=refresh_token -- POST request with grant_type=password First logins by new users Logins to a OneLogin Desktop/Desktop Pro Tray app. - NOTE: Logins to the desktop and to the OneLogin Portal using OneLogin Desktop/OneLogin Desktop Pro will continue to work. Updates to user profiles including: - Adding/Removing authentication factors - Changing/Resetting passwords - Adding Personal apps We highly recommend that you do not perform the above actions during the maintenance window, as they may generate failures or errors. A retry after the database is out of read-only mode should resolve the issue. Please Note: Backend operations that involve database updates such as directory synchronization and application provisioning will be queued and processed after maintenance is completed.

History

No incidents in the last day