Commit 38bb8392 authored by Robert Dubner's avatar Robert Dubner
Browse files

More README.md adjustments.

parent f4e54b87
Pipeline #3632 passed with stage
in 59 minutes and 51 seconds
......@@ -40,7 +40,7 @@ You need to do this before launching `slapd` or `radiusd` to make sure the corre
make scratch
You have to do this once to create a purely local OpenLDAP directory that will be used for the demonstration. Note further that the demonstration uses its own local `slapd.conf` file -- if I did everything right, the demonstration doesn't require any default information, nor will it affect in any way, and OpenLDAP installation on the same computer. It even uses its own TCP/IP port -- port 3899 -- for the demo.
You have to do this once to create a purely local OpenLDAP directory that will be used for the demonstration. Note further that the demonstration uses its own local `slapd.conf` file -- if I did everything right, the demonstration doesn't require any default information, nor will it affect in any way, an OpenLDAP installation on the same computer. It even uses its own TCP/IP port -- port 3899 -- for the demo.
6) Open a terminal window and navigate to `./ldap`. Execute
......@@ -60,5 +60,4 @@ The world being what it is, well, hopefully the error messages in the two termin
Otherwise, well, give me a yell at support@symas.com
Bob Dubner, 2021-10-09
Bob Dubner, October 2021
......@@ -45,8 +45,19 @@ They each end with a `SUCCEEDED` or `FAILED` message.
### One bit of awkwardness
In the sequence of events, when you are getting started, you need to run `make` in this folder *first*, then run `make both` in the `../ldap` terminal window, and *then* run `make rad` here. The reason: in the event that the certificates have been built and put in place the first time, the `slapd` and `radiusd` daemons have to be restarted in order to load those certificates during initialization.
I find it most meaningful to run the `slapd` and `radiusd` daemons, which respond to the `radiusclient`, in their own terminal window. That way, when you run `radiusclient` in its window, you can see that status and any error messages in a side-by-side fashion.
But it is here in the radiusclient/makefile that the certificates get generated and installed. And they have to be in place *before* `slapd` and `radiusd` are launched.
So, assuming you are using two windows:
1) In the `radiusclient` window, run `make`
2) In the `ldap` window, run `make both`. (Remember that you have to run `make scratch` at least *once* before launching `make slapd` or `make both`.)
3) Back in the `radiusclient` window, run `make rad`
Once you have done these various `makes` initially, it all becomes a bit more sensible; you just have to run `make both` in `demonstration/ldap` before you run `make rad` in `demonstration/radiusclient`.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment