https://www.vandenboom.icu/en/tags/ldap/Recent content in LDAP on NotitiesHugo -- gohugo.ioenSat, 09 Mar 2024 17:38:50 +0000https://www.vandenboom.icu/en/blog/2024-configure-ldap-ipa-server-with-jenkins/Sat, 09 Mar 2024 17:38:50 +0000https://www.vandenboom.icu/en/blog/2024-configure-ldap-ipa-server-with-jenkins/=== Identity, Policy, and Audit (IPA) system === Jenkins 2.319.2 === Dashboard -> Security -> Configure Global Security Server: ldap://<IP_SERVER>:389 root DN: dc=,dc=com User search base cn=users,cn=accounts User search filter uid={0} Group search base cn=groups,cn=accounts Group membership -> Search for LDAP groups containing user -> Group membership filter: (| (member={0}) (uniqueMember={0}) (memberUid={1})) Manager DN: uid=<ADMIN_USER>,cn=users,cn=accounts,dc=,dc=comhttps://www.vandenboom.icu/en/blog/2024-configure-ldap-ipa-server-with-nexus/Sat, 09 Mar 2024 17:37:42 +0000https://www.vandenboom.icu/en/blog/2024-configure-ldap-ipa-server-with-nexus/=== Nexus Sonatype Nexus Repository OSS 3.60.0-02 === LDAP ldap://<IP_SERVER>:389 cn=users,cn=accounts,dc=,dc=com Simple Authentication uid=<ADMIN_USER>,cn=users,cn=accounts,dc=,dc=com Next === Select no template User relative DN = leeg User subtree = unchecked Object class: inetOrgPerson User filter = leeg User ID attribute = uid Real name attribute = cn Email attribute = mail Password attribute = leeg Map LDAP groups as roles = uncheckedhttps://www.vandenboom.icu/en/blog/2024-configure-ldap-ipa-server-with-sonarqube/Sat, 09 Mar 2024 17:35:22 +0000https://www.vandenboom.icu/en/blog/2024-configure-ldap-ipa-server-with-sonarqube/Configure LDAP/IPA Server with Sonarqube === Sonarqube 8.9.6 sonar.properties sonarqube-8.9.6/conf/sonar.properties === sonar.security.realm=LDAP ldap.url=ldap://<IP_SERVER>:389 ldap.bindDn=uid=<ADMIN_USER>,cn=users,cn=accounts,dc=,dc=com ldap.bindPassword= ldap.authentication=simple ldap.user.baseDn=cn=users,cn=accounts,dc=,dc=com # laat volgende default # ldap.user.request= # LDAP user request. (default: (&(objectClass=inetOrgPerson)(uid={login})) ) ldap.group.baseDn=cn=groups,cn=accounts,dc=,dc=com # laat volgende default # ldap.group.request= # LDAP group request (default: (&(objectClass=groupOfUniqueNames)(uniqueMember={dn})) )https://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-command-line-searches/Sat, 09 Mar 2024 17:34:27 +0000https://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-command-line-searches/$ ldapsearch -H ldap://<FQDN_SERVER>/ -b dc=,dc=com -x $ ldapsearch -x -LLL -H ldap:/// -b dc=,dc=com dn $ ldapwhoami -x -H ldap:/// $ ldapsearch -H ldap://<IP_SERVER> -D “uid=<ADMIN_USER>,cn=users,cn=compat,dc=,dc=com” -b “cn=users,cn=accounts,dc=,dc=com” -x -W $ ldapsearch -H ldap://<IP_SERVER> -D “uid=<ADMIN_USER>,cn=users,cn=compat,dc=,dc=com” -b “dc=,dc=com” -x -W -s one “(&(objectClass=organizationalUnit) $ ldapsearch -h <FQDN_SERVER> -D ‘uid=<ADMIN_USER>,cn=users,cn=compat,dc=,dc=com’ -o ldif-wrap=no -b ‘dc=,dc=com’ -W uid=<ADMIN_USER> $ ldapsearch -h <FQDN_SERVER> -D ‘uid=,cn=users,cn=compat,dc=,dc=com’ -o ldif-wrap=no -b ‘dc=,dc=com’ -W uid=https://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-client-installation/Sat, 09 Mar 2024 17:33:26 +0000https://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-client-installation/=== # yum install ipa-client # ipa-client-install –server= –domain= –principal=admin -W # ipa-client-install –server=<ipa-server.example.com> –domain=<example.com> –principal=admin -Whttps://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-installation/Sat, 09 Mar 2024 17:31:40 +0000https://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-installation/=== # yum install ipa-server # ipa-server-install === Hosts file aanpassen De FQDN voor op, daarna pas de aliassen /etc/hosts <IP_SERVER> () Mocht er een alias voor de FQDN staan, dan kun je foutmeldingen krijgen die hier niet meteen aan te relateren zijn.https://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-op-red-hat-enterprise-linux-7/Thu, 15 Feb 2024 10:47:28 +0000https://www.vandenboom.icu/en/blog/2024-ldap-ipa-server-op-red-hat-enterprise-linux-7/If you are using a hosts file, make sure it contains FQDNs and pay close attention to the order in which they appear. Check the hosts file and adjust it if necessary: The FQDN must come first, followed by any aliases. /etc/hosts 10.0.0.1 server1.example.com server1 application1 If an alias is listed before the FQDN, you may encounter error messages that are not immediately traceable to this cause.