Skip to content

Commit 23ec116

Browse files
committed
Minor README cleanup
1 parent b9368ba commit 23ec116

File tree

1 file changed

+1
-25
lines changed

1 file changed

+1
-25
lines changed

README.md

Lines changed: 1 addition & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ INSERT INTO includegroups(parentgroupid, includegroupid) VALUES(5504, 5502);
5353
INSERT INTO includegroups(parentgroupid, includegroupid) VALUES(5504, 5501);
5454
INSERT INTO users(name, uidnumber, primarygroup, passsha256) VALUES('hackers', 5001, 5501, '6478579e37aff45f013e14eeb30b3cc56c72ccdc310123bcdf53e0333e3f416a');
5555
INSERT INTO users(name, uidnumber, primarygroup, passsha256) VALUES('johndoe', 5002, 5502, '6478579e37aff45f013e14eeb30b3cc56c72ccdc310123bcdf53e0333e3f416a');
56-
INSERT INTO users(name, mail, uidnumber, primarygroup, passsha256) VALUES('serviceuser', "[email protected]", 5003, 5502, '652c7dc687d98c9889304ed2e408c74b611e86a40caa51c4b43f1dd5913c5cd0');
56+
INSERT INTO users(name, mail, uidnumber, primarygroup, passsha256) VALUES('serviceuser', '[email protected]', 5003, 5502, '652c7dc687d98c9889304ed2e408c74b611e86a40caa51c4b43f1dd5913c5cd0');
5757
INSERT INTO users(name, uidnumber, primarygroup, passsha256, othergroups, custattr) VALUES('user4', 5004, 5504, '652c7dc687d98c9889304ed2e408c74b611e86a40caa51c4b43f1dd5913c5cd0', '5505,5506', '{"employeetype":["Intern","Temp"],"employeenumber":[12345,54321]}');
5858
INSERT INTO capabilities(userid, action, object) VALUES(5001, "search", "ou=superheros,dc=glauth,dc=com");
5959
INSERT INTO capabilities(userid, action, object) VALUES(5003, "search", "*");
@@ -158,27 +158,3 @@ Alternatively, in Postgres and MySQL, we could rely on the database engine's bui
158158
**So, what's the decision?**
159159

160160
In GLAuth 2.x, when including information that does not benefit from being normalized (e.g. custom attributes) we are following the "nosql" trend (irony!) of storing this data in a JSON structure.
161-
162-
## PAM Plugin
163-
164-
To authenticate against local users, edit the configuration file (see pkg/plugins/sample-pam.cfg) so that:
165-
166-
```
167-
...
168-
[backend]
169-
datastore = "plugin"
170-
plugin = "bin/pam.so"
171-
...
172-
```
173-
174-
When building this plugin, one must first ensure that the proper development headers are installed. For instance, on Ubuntu:
175-
```
176-
sudo apt-get install libpam0g-dev
177-
```
178-
179-
You will likely also wish to tweak the `groupWithSearchCapability` setting, to assign an appropriate secondary group.
180-
181-
Then, to perform a search:
182-
```
183-
ldapsearch -LLL -H ldap://localhost:3893 -D cn=<unix user name>,ou=<a group the user belongs to>,dc=glauth,dc=com -w <unix user password> -x -bdc=glauth,dc=com cn=<unix user name>
184-
```

0 commit comments

Comments
 (0)