Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
SetupOpenVPN
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CSD
public
SetupOpenVPN
Commits
df5a50bc
Commit
df5a50bc
authored
5 years ago
by
Administrator
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
73bc92f9
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+17
-6
17 additions, 6 deletions
README.md
with
17 additions
and
6 deletions
README.md
+
17
−
6
View file @
df5a50bc
...
...
@@ -17,7 +17,7 @@ We also assume that:
*
*openvpn*
has a public IP address (
`1.2.3.4`
) as well as a private address
`10.9.8.8`
*
*authca*
has only a private address
`10.9.8.7`
*
this package has been installed (
`git clone`
) under
`/home/Ansible/`
Step 0: repeat each time
------------------------
...
...
@@ -125,9 +125,9 @@ At this point, both servers are ready to process client certificates.
Step 4: Client Configuration
----------------------------
Repeat this step each time you need to issue a new client
configuration file
for OpenVPN (.ovpn file). The .ovpn file is self-contained,
namely it includes
all required files (ca.crt, dh.pem, ta.key).
Repeat this step
and the following one
each time you need to issue a new client
configuration file
for OpenVPN (.ovpn file). The .ovpn file is self-contained,
namely it includes
all required files (ca.crt, dh.pem, ta.key).
### Step 4a: Update Ansible configuration
...
...
@@ -137,6 +137,8 @@ In the following example we are adding a stanza for a configuration for `misterX
```
...
clientconfig:
...
cfghome: /home/ubuntu/configuration-files
...
clients:
...
...
...
@@ -146,8 +148,17 @@ In the following example we are adding a stanza for a configuration for `misterX
```
Note that:
*
`nameshort`
should not contain blanks
*
`CommonName`
is enclosed in single and double quotes
*
`cfghome`
points to the directory where configuration files will be
accumulated
*
under
`clients:`
*
the first line of each stanza is just the name of the stanza, has no particular meaning;
*
`nameshort`
should not contain blanks. Note that this will also be the name
of the resulting configuration file: choose it wisely so it's easy to
distinguish this one from other configuration files you (or tour user) may
be using;
*
`CommonName`
is enclosed in single and double quotes: this, too, has no
particular meaning as it will only be shown when querying the certificate
contained in the resulting configuration file.
### Step 4b: Generate client certificate
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment