Skip to content

Commit 7b0c6fe

Browse files
author
Eric Sethna
authored
Update backup.rst
1 parent 848f34d commit 7b0c6fe

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

source/administration/backup.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ In each case, the user cannot reach the SSO provider, and cannot log in. In this
7878

7979
1) Configure your SSO provider for high availability
8080

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>`_
8282

8383
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.
8484

0 commit comments

Comments
 (0)