AbsaOSS / AbsaOSS/enceladus

Investigate why LDAP Channel Binding breaks authentication

Open
#2,220 1 comment 0 reactions 0 assignees View on GitHub
bug Menas priority: high security
Dominant language
Scala
Stars
33
Forks
16
PR merge metrics
No merged PRs in 30d

Description

## Describe the bug
When LDAP Channel Binding is switched on on the server, it breaks authentication of Menas

## Expected behavior
LDAP Channel Binding setup does not break the application

## Screenshots
```bash
[WARN] 2024-09-10 20:04:48,754 [https-openssl-apr-8443-exec-1] za.co.absa.enceladus.menas.auth.MenasAuthenticationFailureHandler - Authentication exception
za.co.absa.enceladus.menas.auth.exceptions.BadLdapHostException: java.security.PrivilegedActionException: javax.naming.AuthenticationException: [LDAP: error code 49 - 80090346: LdapErr: DSID-0C0905E4, comment: AcceptSecurityContext error, data 80090346, v3839^@]
```

```bash
[INFO]  2024-08-23 05:02:26,121 [main] org.springframework.ldap.core.support.AbstractContextSource - Property 'userDn' not set - anonymous context will be used for read-write operations
[INFO]  2024-08-23 05:29:07,914 [https-openssl-apr-8443-exec-8] org.springframework.ldap.core.support.AbstractContextSource - Property 'userDn' not set - anonymous context will be used for read-write operations
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.