Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update multiserver_setup.md #636

Merged
merged 2 commits into from
Oct 17, 2024
Merged

Update multiserver_setup.md #636

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ce6a608
Update multiserver_setup.md
pkarc Oct 15, 2024
cb91ce9
Update multiserver_setup.md
LaurenceJJones Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion crowdsec-docs/unversioned/user_guides/multiserver_setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ A typical multi server setup should thus have:
- The agent should be registered to the local api

**Using login/password authentication**
- By running `cscli machines add MyMachine` on the LAPI (and c/c the generated credentials to the agent)
- By running `cscli machines add MyMachine` on the LAPI (and copy the generated credentials to the agent)
- or by running `cscli lapi register --machine MyMachine --url http://<lapi>` on the agent and accepting the machine from LAPI with `cscli machines validate MyMachine`

**Using client cert authentication**
Expand Down
Loading