Server on Notities

Network routing to LAN systems with OpenVPN Server

Sat, 15 Nov 2025 15:40:22 +0100

To be able to access systems on the LAN network through the VPN tunnel of the OpenVPN server, the LAN system must know that traffic destined for the VPN subnet must be sent via the OpenVPN server. Without this additional route, return traffic will not reach the VPN clients.

In this example, we use the subnet 10.0.8.0/24 as the IP range you have configured for the OpenVPN tunnel. This is the network in which all VPN clients receive an IP address. To ensure that a device on the LAN can correctly send traffic back to these VPN clients, you must add a static route on that LAN device.

Configure LDAP/IPA Server with Jenkins

Sat, 09 Mar 2024 17:38:50 +0000

===

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=com

Configure LDAP/IPA Server with Nexus

Sat, 09 Mar 2024 17:37:42 +0000

===

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

===

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 = unchecked

Configure LDAP/IPA Server with Sonarqube

Sat, 09 Mar 2024 17:35:22 +0000

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})) )

LDAP/IPA Server command line searches

Sat, 09 Mar 2024 17:34:27 +0000

$ 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=

LDAP/IPA Server client installation

Sat, 09 Mar 2024 17:33:26 +0000

===

# 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 -W

LDAP/IPA Server installation

Sat, 09 Mar 2024 17:31:40 +0000

===

# 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.

LDAP/IPA - Server on Red Hat Enterprise Linux 7

Thu, 15 Feb 2024 10:47:28 +0000

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.

Automatically log in to a Linux server using PuTTY on Windows

Fri, 17 Feb 2023 14:51:15 +0000

You can automatically log in to a Linux server on Windows using PuTTY by making use of a key file. Below I explain step by step how to do this.

Create a key: start: puttygen.exe
Click on: Generate
Click on: Save private key
Go to PuTTY Configuration -> Session
Load a previously created session or create a new one
Go to: Connection -> SSH -> Auth -> Private key file for authentication -> Browse
Select your file with the private key: *.ppk
Go back to Session and click on: Save
Log in to the Linux server using the Saved Sessions and still with your password
Create a new directory in the home directory: .ssh
Give this directory the correct permissions: chmod 700 ~/.ssh
Create and edit the file authorized_keys: vi ~/ssh/authorized_keys
Copy the Public key for pasting from the PuTTY Key Generator
Paste it into the authorized_keys file on the Linux server
Save the authorized_keys file (for vi type: :wq)
Give this file the correct permissions: chmod 600 ~/.ssh/authorized_keys
Close the logged-in PuTTY session to the Linux Server
Open the session again to verify that you can now log in automatically