You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INSERT INTO capabilities(userid, action, object) VALUES(5001, "search", "ou=superheros,dc=glauth,dc=com");
59
59
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
158
158
**So, what's the decision?**
159
159
160
160
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>
0 commit comments