Hi Gerald, thanks, works like a charm.
Mit vielen freundlichen Grüßen, Alexander Ninnig Rechnungshof Rheinland-Pfalz Gerhart-Hauptmann-Straße 4 67346 Speyer Phone: +49(0)6232/617-285 Fax: +49(0)6232/617-100 Mail: alexander.nin...@rechnungshof.rlp.de Web: https://rechnungshof.rlp.de/ -----Ursprüngliche Nachricht----- Von: Rohrbach, Gerald <g.rohrb...@funkegruppe.de> Gesendet: Mittwoch, 6. Mai 2020 15:26 An: user@openmeetings.apache.org Betreff: AW: OpenMeeting 5.0.0-M4, LDAP-connection recognizes "Deutschland" as "Andorra" Alexander, if I remember right you need to use c instead of co. Look at AD attributes under the user. c = DE With that the mapping will work in OM Gerald -----Ursprüngliche Nachricht----- Von: Ninnig, Alexander [mailto:alexander.nin...@rechnungshof.rlp.de] Gesendet: Mittwoch, 6. Mai 2020 15:09 An: user@openmeetings.apache.org Betreff: OpenMeeting 5.0.0-M4, LDAP-connection recognizes "Deutschland" as "Andorra" Hi, I managed to get a working LDAP-connection. But OpenMeetings gets the country wrong. All my users have the country "Deutschland", which is a drop-down-menue in Active Directory, so there's no chance of misspelling. This AD-attribute is "co". In my om_ldap.conf, the corresponding line is: "ldap_user_attr_country=co", so that's correct. But after logging in using this LDAP-connection, German users have "Andorra" as country, not "Deutschland". Can I fix this myself? AD provides a country-code (for Germany, this would be 276). Can OpenMeetings use this instead? Side-question (not directly related to the country-question): Are there more ldap_user_attributes I could use (other than mentioned in the om_ldap.cfg)? Best regards, Alex
