Ryan Richard d2251d2ea7 Use base64 binary-encoded value as UID for LDAP ... This is to allow the use of binary LDAP entry attributes as the UID. For example, a user might like to configure AD’s objectGUID or maybe objectSid attributes as the UID attribute. This negatively impacts the readability of the UID when it did not come from a binary value, but we're considering this an okay trade-off to keep things simple for now. In the future, we may offer more customizable encoding options for binary attributes. These UIDs are currently only used in the downstream OIDC `sub` claim. They do not effect the user's identity on the Kubernetes cluster, which is only based on their mapped username and group memberships from the upstream identity provider. We are not currently supporting any special encoding for those username and group name LDAP attributes, so their values in the LDAP entry must be ASCII or UTF-8 in order for them to be interpreted correctly.		2021-05-27 13:47:10 -07:00
..
cluster_capabilities	Add hasExternalLoadBalancerProvider to AKS/EKS capabilities files	2021-03-26 08:03:51 -07:00
deploy/tools	Add user search base to downstream subject for upstream LDAP	2021-05-26 17:04:20 -07:00
integration	Use base64 binary-encoded value as UID for LDAP	2021-05-27 13:47:10 -07:00
library	Add integration test for LDAP StartTLS	2021-05-20 13:39:48 -07:00