ahaenggli/AzureAD-LDAP-wrapper v2.0.2

on GitHub

[2.0.2] - 2024-06-01

Changed

• updated npm dependencies
• renamed Azure, AzureAD, ... to Microsoft Entra ID

Fixed

• Checked and fixed all links throughout the application.
• Resolved issue #68, ensuring that the container can start even if the original JSON is corrupt.

Added

• usage examples for Portainer, Authelia and Synology Radius with UniFi in the documentation
• Introducing new environment variable LDAP_USERS_SYNCONLYINGROUP:
  • When set, only users within the specified groups are fetched and made available in the wrapper.
  • Multiple group names can be specified using the pipe character (|).
  • This addresses also issue #65. The variable can be used in conjunction with LDAP_USERS_SETDEFAULTGROUP (the next new one).
• New environment variable LDAP_USERS_SETDEFAULTGROUP:
  • When set, the first specified group associated with the user will be used as the default group.
  • Multiple group names can be specified using the pipe character (|).
  • For example, admins|finance|hr. If a user is within both groups (finance and hr), the default group will be set to finance because it was defined first.
  • With DSM 7, there are some issues regarding group permissions (#47). ACL and UID/GID shifting can help. However, when losing the permissions, there seems to be some sort of fallback to the default group. With this setting, you can adjust the default group for your users.
• Experimental environment variable LDAP_DOMAIN_OU:
  • In a tenant with multiple domains, the same username can also be used multiple times (issue #74)
  • When the env var is set, the domain name for each user is appended in the username as ou=domain.tld
    So instead of cn=bob it will become cn=bob,ou=domain.tld. This way bob from domain1 and domain2 can be separated
    by bob,ou=domain1.tld and bob,ou=domain2.tld.
  • The feature is only experimental. There will be changes in handling the different domains.