You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/administration/backup.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ In each case, the user cannot reach the SSO provider, and cannot log in. In this
78
78
79
79
1) Configure your SSO provider for high availability
80
80
81
-
If you're using a self-hosted single-sign-on provider like Active Directory, several options are available for `high availability configurations that protect your system from unplanned outages. <https://docs.microsoft.com/en-us/microsoft-identity-manager/pam/high-availability-disaster-recovery-considerations-bastion-environment>`_
81
+
If you're using a self-hosted single-sign-on provider, several options are available for `high availability configurations that protect your system from unplanned outages. <https://docs.microsoft.com/en-us/microsoft-identity-manager/pam/high-availability-disaster-recovery-considerations-bastion-environment>`_
82
82
83
83
For SaaS-based authentication providers, while you still have a dependency on service uptime, you can setup redundacy of source systems from which data is being pulled. For example, with the OneLogin SaaS-based authentication service, you can setup `high availabilty LDAP connectivity <https://support.onelogin.com/hc/en-us/articles/204262680-High-Availability-for-LDAP>`_ to further reduce the chances of an outage.
0 commit comments