LDAP group mappings not working and throw users to default after re-singin

We have ldap integration in our metabase and prior to 0.34.x versions group mapping used to work. Now i can only manually assign groups to users, but after user relogin it drops every other then Default group.

Tried rollback to different version 0.32.x, 0.33.x but nothing changes.
Maybe
We use postgres as internal metabase db.

Hi @artem
Please post “Diagnostic Info” from Admin > Troubleshooting.
Sounds like you’re seeing this issue:
https://github.com/metabase/metabase/issues/7571 - upvote by clicking :+1: on the first post
But that should also have been a problem on earlier versions.

Yep, i checked this issue, but mine is a bit different, in my case even if user have proper ldap group, mapping for mapping for that group resets to Default for him after relogin.

My Diagnostic Info from our test environment which has the same version and connected to same ldap server:

Blockquote
{
“browser-info”: {
“language”: “en-GB”,
“platform”: “MacIntel”,
“userAgent”: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36”,
“vendor”: “Google Inc.”
},
“system-info”: {
“java.runtime.name”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “11.0.5+10”,
“java.vendor”: “AdoptOpenJDK”,
“java.vendor.url”: “https://adoptopenjdk.net/”,
“java.version”: “11.0.5”,
“java.vm.name”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “11.0.5+10”,
“os.name”: “Linux”,
“os.version”: “4.14.146-119.123.amzn2.x86_64”,
“user.language”: “en”,
“user.timezone”: “GMT”
},
“metabase-info”: {
“databases”: [
“h2”
],
“hosting-env”: “unknown”,
“application-database”: “postgres”,
“application-database-details”: {
“database”: {
“name”: “PostgreSQL”,
“version”: “11.4”
},
“jdbc-driver”: {
“name”: “PostgreSQL JDBC Driver”,
“version”: “42.2.8”
}
},
“run-mode”: “prod”,
“version”: {
“date”: “2020-02-25”,
“tag”: “v0.34.3”,
“branch”: “release-0.34.x”,
“hash”: “1a83edb”
},
“settings”: {
“report-timezone”: null
}
}
}

@artem
I’m not sure what could be happening, but there hasn’t been any other reports of problems with LDAP on 0.34.3
You could try enabling debug logging and see if that helps with tracking down the root cause:
https://www.metabase.com/docs/latest/operations-guide/log-configuration.html
Otherwise, open an issue with as many details as possible (and steps to reproduce):
https://github.com/metabase/metabase/issues/new/choose