File tree Expand file tree Collapse file tree 2 files changed +19
-0
lines changed Expand file tree Collapse file tree 2 files changed +19
-0
lines changed Original file line number Diff line number Diff line change
1
+ apiVersion : authentication.stackable.tech/v1alpha1
2
+ kind : AuthenticationClass
3
+ metadata :
4
+ name : kerberos-auth
5
+ spec :
6
+ provider :
7
+ kerberos :
8
+ kerberosSecretClass : kerberos-auth
Original file line number Diff line number Diff line change @@ -18,6 +18,7 @@ The following authentication providers are supported:
18
18
* <<LDAP>>: Authenticate users using an LDAP server.
19
19
* <<OIDC>>: Authenticate users using an OpenID connect provider.
20
20
* <<TLS>>: Authenticate users with client TLS certificates.
21
+ * <<Kerberos>>: Authenticate users with Kerberos keytabs.
21
22
* <<Static>>: Authenticate users against a static list of users and passwords in a simple Kubernetes Secret.
22
23
23
24
[#ldap]
@@ -76,6 +77,16 @@ A sample TLS provider looks as follows:
76
77
include::example$authenticationclass-tls.yaml[]
77
78
----
78
79
80
+ [#kerberos]
81
+ === Kerberos
82
+ The `Kerberos` provider configures a product to authenticate users using Kerberos tickets issued by the Kerberos Key Distribution Center (KDC).
83
+ The Kerberos provider defines `kerberosSecretClass` which points to a Kerberos SecretClass that contains the necessary KDC and realm information:
84
+
85
+ [source,yaml]
86
+ ----
87
+ include::example$authenticationclass-kerberos.yaml[]
88
+ ----
89
+
79
90
[#static]
80
91
=== Static
81
92
The `static` provider is used to represent a simple - static - set of users.
You can’t perform that action at this time.
0 commit comments