From a25ffe5d082d9594c4980b5216ceea4d9c666d3a Mon Sep 17 00:00:00 2001 From: Isan Rivkin Date: Thu, 21 Nov 2024 15:37:45 +0200 Subject: [PATCH 1/2] docs --- docs/security/external-principals-aws.md | 2 +- docs/security/sso.md | 87 +++++++++++++++++++++--- 2 files changed, 79 insertions(+), 10 deletions(-) diff --git a/docs/security/external-principals-aws.md b/docs/security/external-principals-aws.md index 2d6b49b3ed7..80a19c62866 100644 --- a/docs/security/external-principals-aws.md +++ b/docs/security/external-principals-aws.md @@ -159,7 +159,7 @@ for r in repos: ``` -[external-principal-admin]: {% link reference/cli.md %}#external +[external-principal-admin]: {% link reference/api.md %}#external [login-api]: {% link reference/api.md %}#auth/externalPrincipalLogin [lakefs-hadoopfs]: {% link integrations/spark.md %}#lakefs-hadoop-filesystem [lakefs-spark]: {% link integrations/spark.md %}#usage-with-temporaryawscredentialslakefstokenprovider diff --git a/docs/security/sso.md b/docs/security/sso.md index 0990cc9cce7..270763e8a7f 100644 --- a/docs/security/sso.md +++ b/docs/security/sso.md @@ -283,13 +283,31 @@ auth:
## LDAP -In order for Fluffy to work, the following values must be configured. Update (or override) the following attributes in the chart's `values.yaml` file. -1. Replace `lakefsConfig.auth.remote_authenticator.endpoint` with the lakeFS server URL combined with the `api/v1/ldap/login` suffix (e.g `http://lakefs.company.com/api/v1/ldap/login`) -2. Repalce `fluffyConfig.auth.ldap.remote_authenticator.server_endpoint` with your LDAP server endpoint (e.g `ldaps://ldap.ldap-address.com:636`) -3. Replace `fluffyConfig.auth.ldap.remote_authenticator.bind_dn` with the LDAP bind user/permissions to query your LDAP server. -4. Replace `fluffyConfig.auth.ldap.remote_authenticator.user_base_dn` with the user base to search users in. +Fluffy is incharge of providing LDAP authentication for lakeFS Enterprise. +The authentication works by querying the LDAP server for user information and authenticating the user based on the provided credentials. -lakeFS Server Configuration (Update in helm's `values.yaml` file): +**Important:** An administrative bind user must be configured. It should have search permissions for the LDAP server that will be used to query the LDAP server for user information. + +**For Helm:** set the following attributes in the Helm chart values, for lakeFS `lakefsConfig.*` and `fluffyConfig.*` for fluffy. + +**Non-Helm:** If not using Helm use the YAML below to directly update the configuration file for each service. + +**lakeFS Configuration:** + +1. Replace `auth.remote_authenticator.enabled` with `true` +2. Replace `auth.remote_authenticator.endpoint` with the fluffy authentication server URL combined with the `api/v1/ldap/login` suffix (e.g `http://lakefs.company.com/api/v1/ldap/login`) + +**fluffy Configuration:** + +See [Fluffy configuration][fluffy-configuration] reference. + +1. Repalce `auth.ldap.remote_authenticator.server_endpoint` with your LDAP server endpoint (e.g `ldaps://ldap.ldap-address.com:636`) +2. Replace `auth.ldap.remote_authenticator.bind_dn` with the LDAP bind user/permissions to query your LDAP server. +3. Replace `auth.ldap.remote_authenticator.user_base_dn` with the user base to search users in. + +**lakeFS Server Configuration file:** + +`$lakefs run -c ./lakefs.yaml` ```yaml # Important: make sure to include the rest of your lakeFS Configuration here! @@ -305,7 +323,9 @@ auth: - internal_auth_session ``` -Fluffy Configuration (Update in helm's `values.yaml` file): +Fluffy Configuration file: + +`$fluffy run -c ./lakefs.yaml` ```yaml logging: @@ -319,14 +339,62 @@ auth: post_login_redirect_url: / ldap: server_endpoint: 'ldaps://ldap.company.com:636' - bind_dn: uid=,ou=Users,o=,dc=,dc=com + bind_dn: uid=,ou=,o=,dc=,dc=com bind_password: '' username_attribute: uid - user_base_dn: ou=Users,o=,dc=,dc=com + user_base_dn: ou=,o=,dc=,dc=com user_filter: (objectClass=inetOrgPerson) connection_timeout_seconds: 15 request_timeout_seconds: 7 ``` +### Troubleshooting LDAP issues + +**Inspecting Logs** + +If you encounter LDAP connection errors, you should inspect the **fluffy container** logs to get more information. + +**Authentication issues:** + +Auth issues (e.g. user not found, invalid credentials) can be debugged with the [ldapwhoami](https://www.unix.com/man-page/osx/1/ldapwhoami) CLI tool. + +The Examples are based on the fluffy config above: + +1. Verify that the main bind user can connect: + +```sh +ldapwhoami -H ldap://ldap.company.com:636 -D "uid=,ou=,o=,dc=,dc=com" -x -W +``` + +2. Verify that a specific lakeFS user `dev-user` can connect: + +```sh +ldapwhoami -H ldap://ldap.company.com:636 -D "uid=dev-user,ou=,o=,dc=,dc=com" -x -W +``` + +**User not found issue:** + +Upon a login request in fluffy, the bind user will search for the user in the LDAP server. If the user is not found it will be presented in the logs. + +We can search the user using [ldapsearch](https://docs.ldap.com/ldap-sdk/docs/tool-usages/ldapsearch.html) CLI tool. + +Search ALL users in the base DN (no filters): + +**Note:** `-b` is the `user_base_dn`, `-D` is `bind_dn` and `-w` is `bind_password` from the fluffy configuration. + +```sh +ldapsearch -H ldap://ldap.company.com:636 -x -b "ou=,o=,dc=,dc=com" -D "uid=,ou=,o=,dc=,dc=com" -w '' +``` + +If the user is found, we should now use filters for the specific user the same way fluffy does it and expect to see the user. + +For example, to repdocue the same search as fluffy does: +- user `dev-user` set from `uid` attribute in LDAP +- Fluffy configuration values: `user_filter: (objectClass=inetOrgPerson)` and `username_attribute: uid` + +```sh +ldapsearch -H ldap://ldap.company.com:636 -x -b "ou=,o=,dc=,dc=com" -D "uid=,ou=,o=,dc=,dc=com" -w '' "(&(uid=dev-user)(objectClass=inetOrgPerson))" +``` +
@@ -345,3 +413,4 @@ Notes: * Fluffy docker image: replace the `fluffy.image.privateRegistry.secretToken` with real token to dockerhub for the fluffy docker image. [rbac-preconfigured]: {% link security/rbac.md %}#preconfigured-groups +[fluffy-configuration]: {% link enterprise/configuration.md %}#fluffy-server-configuration \ No newline at end of file From feb147eed6cc9b95650c74b650b47c146bf75998 Mon Sep 17 00:00:00 2001 From: Isan Rivkin Date: Thu, 21 Nov 2024 15:48:03 +0200 Subject: [PATCH 2/2] fixes --- docs/security/sso.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/docs/security/sso.md b/docs/security/sso.md index 270763e8a7f..94a3439fa45 100644 --- a/docs/security/sso.md +++ b/docs/security/sso.md @@ -290,7 +290,7 @@ The authentication works by querying the LDAP server for user information and au **For Helm:** set the following attributes in the Helm chart values, for lakeFS `lakefsConfig.*` and `fluffyConfig.*` for fluffy. -**Non-Helm:** If not using Helm use the YAML below to directly update the configuration file for each service. +**No Helm:** If not using Helm use the YAML below to directly update the configuration file for each service. **lakeFS Configuration:** @@ -325,7 +325,7 @@ auth: Fluffy Configuration file: -`$fluffy run -c ./lakefs.yaml` +`$fluffy run -c ./fluffy.yaml` ```yaml logging: @@ -347,31 +347,32 @@ auth: connection_timeout_seconds: 15 request_timeout_seconds: 7 ``` -### Troubleshooting LDAP issues -**Inspecting Logs** +## Troubleshooting LDAP issues + +### Inspecting Logs If you encounter LDAP connection errors, you should inspect the **fluffy container** logs to get more information. -**Authentication issues:** +### Authentication issues Auth issues (e.g. user not found, invalid credentials) can be debugged with the [ldapwhoami](https://www.unix.com/man-page/osx/1/ldapwhoami) CLI tool. The Examples are based on the fluffy config above: -1. Verify that the main bind user can connect: +To verify that the main bind user can connect: ```sh ldapwhoami -H ldap://ldap.company.com:636 -D "uid=,ou=,o=,dc=,dc=com" -x -W ``` -2. Verify that a specific lakeFS user `dev-user` can connect: +To verify that a specific lakeFS user `dev-user` can connect: ```sh ldapwhoami -H ldap://ldap.company.com:636 -D "uid=dev-user,ou=,o=,dc=,dc=com" -x -W ``` -**User not found issue:** +### User not found issue Upon a login request in fluffy, the bind user will search for the user in the LDAP server. If the user is not found it will be presented in the logs.