Sudo apt -assume-yes install pritunl mongodb-server. Once the installation is successfull, hit the below commands to start and enable mongodb services. Sudo systemctl start pritunl mongodb sudo systemctl enable pritunl mongodb Step 4: Configure Pritunl on Ubuntu 20.04. Finally configure the Pritunl VPN by visiting your server IP. Pritunl is an open-source enterprise distributed OpenVPN and IPsec server. OIDC OpenID Connect is an extension to the OAuth standard that. Pritunl VPN is an open source VPN server and management panel. Has a graphical interface (GUI) that provides a friendly interaction to the user.
Usually organizations use an internal network to prevent unauthorized people from connecting to their private network and by using their own network infrastructure/connectivity they can maintain their desirable level of security for their data. But it would be convenient for users to connect to that private network while they are away from the office’s building, on their own internet connection. To solve that problem, VPN (Virtual Private Network)is used to allow authorized remote access to an organization’s private network.
Working in a fully remote company like Mattermost is, creates the need for employees to use a VPN connection in order to be able to access internal private infrastructure and resources. A vast majority of companies use OpenVPN as a solution to host those VPN connections on their own servers. OpenVPN is a widely used software and protocol which was also our selection to be used as a quick and reliable solution to access our internal infrastructure. After using it a while we needed a better solution in terms of:
- High Availability (HA)
- Auditing
- Supporting better access control (e.g. only SREs can access production servers and only developers can access development accounts)
- Working with SSO, particularly OneLoginAfter some investigation, we ended up with Pritunl because:
- It’s built on the OpenVPN protocol
- It’s open source
- The Pritunl client can be installed on any platform
- Its pricing is reasonable for our scale
- It hides the complete configuration (user and server management) overhead behind the scenes of the web interface
Pritunl infrastructure
To deploy Pritunl in our infrastructure, we used Terraform. The module we wrote can be found here as an example for how to deploy Pritunl. The infrastructure consists of:
- One Route53 record
- One network load balancer
- Two AutoScaling Groups (ASGs)
- One MongoDB Atlas
Why two AutoScaling Groups?
The selection of two ASGs with one instance has been done due to the necessity of having the same Elastic Network Interface (ENI), which results on having the same private and public IPs. This is useful when whitelisting those IPs into the Security Groups that Pritunl-VPN needs to access internally such as our internal GitLab.
Usb devices driver download for windows 10. This can be achieved by attaching those ENIs as a secondary network interfaces on the instance, check appendix Attach second ENI.
Trimble navigation laptops & desktops driver. You can manually create two ENIs (we selected the sixth address of each subnet 10.0.0.6
and 10.0.16.6
) and attach public IPs to them. Then you can provide the list of the ENI IDs with the variable (list) fixed_eni
on Terraform.
MongoDB Atlas
Initially, we checked the AWS DocumentDB solution, but it was quite expensive, as it starts from $0.28/hr for one db.r5.large
instance.Next, we deployed two instances and installed/configured a MongoDB cluster, but maintaining and making sure that HA worked effectively was a big overhead.
Thus, we selected to use MongoDB Atlas as it is cheaper (starts also from free tier) and easier to set up.After the creation of the MongoDB Atlas, we added Pritunl’s public IPs on the whitelist of the Atlas cluster and we connected to the Atlas cluster locally to create a new database in it called pritunl
(guide on how-to-connect). Also check Pritunl documentation for MongoDB Atlas.
To set up the MongoDB URI (mongodb+srv://pritunl:password@pritunl-mongodb-xxxxx.mongodb.net/pritunl
) use the variable (string) mongodb_uri
on Terraform.
Network Load Balancer
The Network Load Balancer (NLB) which is in front of the instances which has five listeners as shown below. There are three listeners for VPN (on ports 1194
, 1195
, 1196
) that can be used for the servers inside the Pritunl. Currently, we are using only port 1194
, so the rest are for future usage.
Pritunl configuration
Pritunl is installed via the userdata. As the instances do not store any configuration items except the MongoDB URI, each instance needs to connect to the MongoDB to obtain the required configuration and then the instance joins the Pritunl cluster.
Initial setup
As per Pritunl documentation:
- SSH into one of the Pritunl instances by using Session-manager.
- Run:
sudo pritunl default-password
to get the default username and password. - Navigate to the Pritunl log in page and use the credentials from the previous step.
- Create a user pritunl and add a new password.
Organization and server setup
As per Pritunl documentation:
Navigate to Users and create a new organization, e.g.
devs_org
Navigate to Servers and create a new server:
- Name:
devs_server
- Port:
1194
(or any other port that you have setup for VPN access, check NLB) - DNS Server:
10.0.0.2, 8.8.8.8
where10.0.0.2
is the DNS resolution of the subnet. The second IP of each subnet is used for DNS resolution and our VPC where Pritunl is running has peering with all the other VPCs, so it is able to resolve all the names inside our network. - Save your changes.
- Name:
Remove the
0.0.0.0/0
route from thedevs_server
.Select Attach Organization to attach
devs_org
withdevs_server
. Tops laptops & desktops driver download for windows.Select Attach host to attach the two hosts (instances).
Select Add Route (ensure that the server points to
devs_server
).- You’ll need to add the DNS resolution as we have set it up above on the
DNS Server
:- 10.0.0.2/32 DNS resolution
- You’ll need to add all the routes that this server will need to access (i.e. other VPCs)(add routes and each comment for clarity)e.g.:
- 10.8.0.0/16 prod VPC
- 10.16.0.0/16 staging VPC
- Wherever else you want the Pritunl/VPN to have access.
- You’ll need to add the DNS resolution as we have set it up above on the
Start the server with
Start Server
button
Enabling OneLogin
To enable Onelogin, Pritunl Enterprise (with subscription) is needed, otherwise the configuration won’t display in the Settings. Then, you will need to set up a new app inside OneLogin (admin access is needed) and you will need to paste that information inside Pritunl:
- Single Sign-On:
OneLogin
- OneLogin App ID:
1234567
- SAML Sign-On URL:
https://your-company.onelogin.com/trust/saml2/http-redirect/sso/xxxx-xxxx-xxxx-xxxx
- SAML Issuer URL:
https://app.onelogin.com/saml/metadata/xxxx-xxxx-xxxx-xxxx
- OneLogin API Client ID, OneLogin API Client Secret, and the SAML Certificate.
Appendix
Attach second ENI
Below is the bash script to attach a second ENI for Ubuntu 18.04 as per AWS documentation.
That script can be used widely for other purposes, as well.
Pritunl API sample
In order to invoke the Pritunl API, we had to make some changes on the python code that exists here as below:
Written by Angelos Kyratzakos- @angelos.kyratzakoson community.mattermost.comand @angeloskyratzakoson GitHub