documentations for Configurable ODBC...
36.2 Configurable ODBC
The ODBC database has to have two table, or two views, one for entities and one for groups.
The entity table must have the four following fields: entityid, name, descr and email. The fields name,
descr and email must be strings. Entityid must be a unique identifier (suitable for primary key).
The groups table must contain two fields: groupid and memberid. Together these two fields create a
The 'memberid' should contain the 'uid' and the 'groups' info should contain the name on the group.
Ok, so bottomline, the documentation is completely unhelpful. I worked through the group resolution issue and as far as I'm concerned it's a bug.
The world I'm supporting has many many users, so many that using a bigint datatype for the entityid is required. When doing user resolution, having the bigint works without issue.
However, try to get a bigint working in the groups table and you are going to find that group resolution won't work. The reason is that while you can make the memberid and groupid a bigint, the code for reading the fields will only recognize values up to max(int) or approximately 2.1 billion. My opinion, this is a big ole bug that hopefully will be addressed soon.