public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

minor spacing issues

Browse Source
This commit is contained in:
Marty Hernandez Avedon
2023-03-09 17:37:47 -05:00
committed by GitHub
parent ae0cb3ecc6
commit 70f38c0bc9
1 changed files with 7 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages-for-subheaders/authentication-config.md
+7 -9
View File
@@ -112,14 +112,13 @@ is logged in to Rancher as an external user, not the local admin.
## Disabling An Auth Provider
When you disable an auth provider, Rancher deletes all resources associated with it, such as:
- Secrets
- Global role bindings
- Cluster role template bindings
- Project role template bindings
- External users associated with the provider, who never logged in as local users to Rancher
- Secrets.
- Global role bindings.
- Cluster role template bindings.
- Project role template bindings.
- External users associated with the provider, but who never logged in as local users to Rancher.
As this operation may lead to a loss of many resources, you may want to add a safeguard on the provider.
To ensure this cleanup process doesn't run when the auth provider is disabled, add a special annoation to the corresponding auth config.
As this operation may lead to a loss of many resources, you may want to add a safeguard on the provider. To ensure that this cleanup process doesn't run when the auth provider is disabled, add a special annotation to the corresponding auth config.
For example, to add a safeguard to the Azure AD provider, annotate the `azuread` authconfig object:
@@ -131,5 +130,4 @@ Rancher won't perform cleanup until you set the annotation to `unlocked`.
Rancher might retain resources from a previously disabled auth provider configuration in the local cluster, even after you configure another auth provider. For example, if you used Provider A, then disabled it and started using Provider B, when you upgrade to a new version of Rancher, you can manually trigger cleanup on resources configured by Provider A.
To manually trigger cleanup for a disabled auth provider, add the `management.cattle.io/auth-provider-cleanup` annotation with the `unlocked` value
to its auth config.
To manually trigger cleanup for a disabled auth provider, add the `management.cattle.io/auth-provider-cleanup` annotation with the `unlocked` value to its auth config.