# Issue with LDAP Login Using Usernames Containing a Dot (e.g., j.doe)

**URL:** <https://discuss.codelibs.org/t/issue-with-ldap-login-using-usernames-containing-a-dot-e-g-j-doe/2599>\
**Category:** English:Fess\
**Created:** [February 10, 2025, 11:24am UTC](https://discuss.codelibs.org/t/issue-with-ldap-login-using-usernames-containing-a-dot-e-g-j-doe/2599 "2025-02-10T11:24:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZwiebelritterAG](https://discuss.codelibs.org/letter_avatar_proxy/v4/letter/z/db5fbb/32.png) [@ZwiebelritterAG](https://discuss.codelibs.org/u/ZwiebelritterAG)\
**Post date:** [February 10, 2025, 11:24am UTC](https://discuss.codelibs.org/t/issue-with-ldap-login-using-usernames-containing-a-dot-e-g-j-doe/2599/1 "2025-02-10T11:24:28Z")

</div>

Hello,

I am facing an issue with LDAP integration on my Fess server. The configuration works perfectly for users whose `sAMAccountName` does not contain a dot (e.g., `doe`), but fails for users with a dot in their username (e.g., `j.doe`).

### Environment

- **Fess version:** [Insert your Fess version]
- **LDAP Server:** Active Directory
- **LDAP URL:** `ldap://192.168.8.12:389`
- **Base DN:** `OU=Users,OU=SUB,DC=test-domain,DC=de`
- **User DN:** `%s@test-domain.com`
- **Account Filter:** `(&(objectClass=user)(sAMAccountName=%s))`
- **Group Filter:** `(objectClass=group)`

### Issue Description

1. Users with `sAMAccountName` as `doe` can successfully log in and their permissions are retrieved:

```auto
action:LOGIN user:doe permissions:2Drucker Verteiler GAT|... time:2025-02-10T10:50:38.048882367Z

```

1. However, users with `sAMAccountName` as `j.doe` cannot retrieve permissions and see no search results:

```auto
action:LOGIN user:j.doe permissions:1j.doe time:2025-02-10T10:51:10.406688595Z

```

It seems that the dot (`.`) in the username is causing the issue.

1. Even after modifying the LDAP filters (e.g., allowing `userPrincipalName` or escaping the dot in `sAMAccountName`), the problem persists. The groups and permissions are not loaded for these users.

### Expected Behavior

Users with a dot in their username (e.g., `j.doe`) should be able to log in and their group permissions should be correctly retrieved.

### Actual Behavior

Users with a dot in their username can log in but their group permissions are not retrieved, resulting in no search results being shown.

### Question

Is there a known issue with Fess handling usernames containing dots (`.`) when using LDAP? How can I ensure that users with such usernames can log in and have their permissions correctly loaded?

Thank you for your support!

---

<div class="post-metadata">

**Author:** ![shinsuke](https://discuss.codelibs.org/user_avatar/discuss.codelibs.org/shinsuke/32/6_2.png) [@shinsuke](https://discuss.codelibs.org/u/shinsuke)\
**Post date:** [February 20, 2025, 1:24am UTC](https://discuss.codelibs.org/t/issue-with-ldap-login-using-usernames-containing-a-dot-e-g-j-doe/2599/2 "2025-02-20T01:24:33Z")

</div>

We have tested it, but we were unable to reproduce the issue. Users with a dot in their username (e.g., j.doe) can log in and retrieve permissions correctly.

```auto
action:LOGIN user:doe permissions:1doe|2GroupA ip:0:0:0:0:0:0:0:1 time:2025-02-19T10:46:48.281764800Z
action:LOGOUT user:doe permissions:1doe|2GroupA ip:0:0:0:0:0:0:0:1 time:2025-02-19T10:46:54.389730300Z
action:LOGIN user:j.doe permissions:1j.doe|2GroupA ip:0:0:0:0:0:0:0:1 time:2025-02-19T10:47:11.424043300Z
action:LOGOUT user:j.doe permissions:1j.doe|2GroupA ip:0:0:0:0:0:0:0:1 time:2025-02-19T10:47:15.437104800Z

```

---

<div class="post-metadata">

**Author:** ![system](https://discuss.codelibs.org/uploads/default/original/1X/efce8754755b16f7cd29d67032acc350fe50e37e.png) [@system](https://discuss.codelibs.org/u/system)\
**Post date:** [May 21, 2025, 1:24am UTC](https://discuss.codelibs.org/t/issue-with-ldap-login-using-usernames-containing-a-dot-e-g-j-doe/2599/3 "2025-05-21T01:24:43Z")

</div>

Closed on May 21, 2025, 1:24am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.