/
README
413 lines (307 loc) · 16.2 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
NAME
RT::Extension::LDAPImport - Import Users from an LDAP store
SYNOPSIS
In "RT_SiteConfig.pm":
Set($LDAPHost,'my.ldap.host')
Set($LDAPUser,'me');
Set($LDAPPassword,'mypass');
Set($LDAPFilter, '(&(cn = users))');
Set($LDAPMapping, {Name => 'uid', # required
EmailAddress => 'mail',
RealName => 'cn',
WorkPhone => 'telephoneNumber',
Organization => 'departmentName'});
# Add to any existing plugins
Set(@Plugins, qw(RT::Extension::LDAPImport));
# If you want to sync Groups RT <-> LDAP
Set($LDAPGroupBase, 'ou=Groups,o=Our Place');
Set($LDAPGroupFilter, '(&(cn = Groups))');
Set($LDAPGroupMapping, {Name => 'cn',
Member_Attr => 'member',
Member_Attr_Value => 'dn' });
Running the import:
# Run a test import
/opt/rt4/local/plugins/RT-Extension-LDAPImport/bin/rtldapimport \
--debug > ldapimport.debug 2>&1
# Run for real, possibly put in cron
/opt/rt4/local/plugins/RT-Extension-LDAPImport/bin/rtldapimport \
--import
CONFIGURATION
All of the configuration for the importer goes your "RT_SiteConfig.pm"
file. Some of these values pass through to Net::LDAP so you can check
there for valid values and more advanced options.
"Set($LDAPHost,'our.ldap.host');"
Hostname or ldap(s):// uri:
"Set($LDAPUser, 'uid=foo,ou=users,dc=example,dc=com');"
Your LDAP username or DN. If unset, we'll attempt an anonymous bind.
"Set($LDAPPassword, 'ldap pass');"
Your LDAP password.
"Set($LDAPBase, 'ou=People,o=Our Place');"
Base object to search from.
"Set($LDAPFilter, '(&(cn = users))');"
The LDAP search filter to apply (in this case, find all the users).
"Set($LDAPMapping..."
Set($LDAPMapping, {Name => 'uid',
EmailAddress => 'mail',
RealName => 'cn',
WorkPhone => 'telephoneNumber',
Organization => 'departmentName'});
This provides the mapping of attributes in RT to attribute in LDAP.
Only Name is required for RT.
The LDAP attributes can also be an arrayref of LDAP fields
WorkPhone => [qw/CompanyPhone Extension/]
which will be concatenated together with a space.
The LDAP attribute can also be a subroutine reference that returns
either an arrayref or a list of attributes.
The keys in the mapping (i.e. the RT fields, the left hand side) may
be a user custom field name prefixed with "UserCF.", for example
"'UserCF.Employee Number' => 'employeeId'". Note that this only adds
values at the moment, which on single value CFs will remove any old
value first. Multiple value CFs may behave not quite how you expect.
If the attribute no longer exists on a user in LDAP, it will be
cleared on the RT side as well.
You may also prefix any RT custom field name with "CF." inside your
mapping to add available values to a Select custom field. This
effectively takes user attributes in LDAP and adds the values as
selectable options in a CF. It does not set a CF value on any RT
object (User, Ticket, Queue, etc). You might use this to populate a
ticket Location CF with all the locations of your users so that
tickets can be associated with the locations in use.
"Set($LDAPCreatePrivileged, 1);"
By default users are created as Unprivileged, but you can change
this by setting $LDAPCreatePrivileged to 1.
"Set($LDAPGroupName,'My Imported Users');"
The RT Group new and updated users belong to. By default, all users
added or updated by the importer will belong to the 'Imported from
LDAP' group.
"Set($LDAPSkipAutogeneratedGroup, 1);"
Set this to true to prevent users from being automatically added to
the group configured by $LDAPGroupName.
"Set($LDAPUpdateUsers, 1);"
By default, existing users are skipped. If you turn on
LDAPUpdateUsers, we will clobber existing data with data from LDAP.
"Set($LDAPUpdateOnly, 1);"
By default, we create users who don't exist in RT but do match your
LDAP filter and obey $LDAPUpdateUsers for existing users. This
setting updates existing users, overriding $LDAPUpdateUsers, but
won't create new users who are found in LDAP but not in RT.
"Set($LDAPGroupBase, 'ou=Groups,o=Our Place');"
Where to search for groups to import.
"Set($LDAPGroupFilter, '(&(cn = Groups))');"
The search filter to apply.
"Set($LDAPGroupMapping..."
Set($LDAPGroupMapping, {Name => 'cn',
Member_Attr => 'member',
Member_Attr_Value => 'dn' });
A mapping of RT attributes to LDAP attributes to identify group
members. Name will become the name of the group in RT, in this case
pulling from the cn attribute on the LDAP group record returned.
"Member_Attr" is the field in the LDAP group record the importer
should look at for group members. These values (there may be
multiple members) will then be compared to the RT user name, which
came from the LDAP user record.
"Member_Attr_Value", which defaults to 'dn', specifies where on the
LDAP user record the importer should look to compare the member
value. A match between the member field on the group record and this
identifier (dn or other LDAP field) on a user record means the user
will be added to that group in RT.
You can provide a "Description" key which will be added as the group
description in RT. The default description is 'Imported from LDAP'.
"Set($LDAPSizeLimit, 1000);"
You can set this value if your LDAP server has result size limits.
Mapping Groups Between RT and LDAP
If you are using the importer, you likely want to manage access via LDAP
by putting people in groups like 'DBAs' and 'IT Support', but also have
groups for other non-RT related things. In this case, you won't want to
create all of your LDAP groups in RT. To limit the groups that get
mirrored, construct your $LDAPGroupFilter as an OR (|) with all of the
RT groups you want to mirror from LDAP. For example:
Set($LDAPGroupBase, 'OU=Groups,OU=Company,DC=COM');
Set($LDAPGroupFilter, '(|(CN=DBAs)(CN=IT Support))');
The importer will then import only the groups that match. In this case,
import means:
* Verifying the group is in AD;
* Creating the group in RT if it doesn't exist;
* Populating the group with the members identified in AD;
The import script will also issue a warning if a user isn't found in RT,
but this should only happen when testing. When running with --import on,
users are created before groups are processed, so all users (group
members) should exist unless there are inconsistencies in your LDAP
configuration.
Running the Import
Executing "rtldapimport" will run a test that connects to your LDAP
server and prints out a list of the users found. To see more about these
users, and to see more general debug information, include the "--debug"
flag.
That debug information is also sent to the RT log with the debug level.
Errors are logged to the screen and to the RT log.
Executing "rtldapimport" with the "--import" flag will cause it to
import users into your RT database. It is recommended that you make a
database backup before doing this. If your filters aren't set properly
this could create a lot of users or groups in your RT instance.
RT Versions
The importer works with RT 3.8 and newer including RT 4.
It may work with RT 3.6.
LDAP Filters
The ldapsearch
<http://www.openldap.org/software/man.cgi?query=ldapsearch&manpath=OpenL
DAP+2.0-Release> utility in openldap can be very helpful while refining
your filters.
METHODS
connect_ldap
Relies on the config variables $RT::LDAPHost, $RT::LDAPUser and
$RT::LDAPPassword being set in your RT Config files.
Set($LDAPHost,'my.ldap.host')
Set($LDAPUSER,'me');
Set($LDAPPassword,'mypass');
LDAPUser and LDAPPassword can be blank, which will cause an anonymous
bind.
LDAPHost can be a hostname or an ldap:// ldaps:// uri.
run_user_search
Set up the appropriate arguments for a listing of users.
_run_search
Executes a search using the provided base and filter.
Will connect to LDAP server using "connect_ldap".
Returns an array of Net::LDAP::Entry objects, possibly consolidated from
multiple LDAP pages.
import_users import => 1|0
Takes the results of the search from run_search and maps attributes from
LDAP into "RT::User" attributes using $RT::LDAPMapping. Creates RT users
if they don't already exist.
With no arguments, only prints debugging information. Pass "--import" to
actually change data.
$RT::LDAPMapping> should be set in your "RT_SiteConfig.pm" file and look
like this.
Set($LDAPMapping, { RTUserField => LDAPField, RTUserField => LDAPField });
RTUserField is the name of a field on an "RT::User" object LDAPField can
be a simple scalar and that attribute will be looked up in LDAP.
It can also be an arrayref, in which case each of the elements will be
evaluated in turn. Scalars will be looked up in LDAP and concatenated
together with a single space.
If the value is a sub reference, it will be executed. The sub should
return a scalar, which will be examined. If it is a scalar, the value
will be looked up in LDAP. If it is an arrayref, the values will be
concatenated together with a single space.
By default users are created as Unprivileged, but you can change this by
setting $LDAPCreatePrivileged to 1.
_import_user
The user has run us with --import, so bring data in.
_cache_user ldap_entry => Net::LDAP::Entry, [user => { ... }]
Adds the user to a global cache which is used when importing groups
later.
Optionally takes a second argument which is a user data object returned
by _build_user_object. If not given, _cache_user will call
_build_user_object itself.
Returns the user Name.
_check_ldap_mapping
Returns true is there is an "LDAPMapping" configured, returns false,
logs an error and disconnects from ldap if there is no mapping.
_build_user_object
Utility method which wraps "_build_object" to provide sane defaults for
building users. It also tries to ensure a Name exists in the returned
object.
_build_object
Builds up data from LDAP for importing Returns a hash of user or group
data ready for "RT::User::Create" or "RT::Group::Create".
_parse_ldap_mapping
Internal helper function for "import_user". If we're passed an arrayref,
it will recurse over each of the elements in case one of them is another
arrayref or subroutine.
If we're passed a subref, it executes the code and recurses over each of
the returned values so that a returned array or arrayref will work.
If we're passed a scalar, returns that.
Returns a list of values that need to be concatenated together.
create_rt_user
Takes a hashref of args to pass to "RT::User::Create" Will try loading
the user and will only create a new user if it can't find an existing
user with the "Name" or "EmailAddress" arg passed in.
If the $LDAPUpdateUsers variable is true, data in RT will be clobbered
with data in LDAP. Otherwise we will skip to the next user.
If $LDAPUpdateOnly is true, we will not create new users but we will
update existing ones.
add_user_to_group
Adds new users to the group specified in the $LDAPGroupName variable
(defaults to 'Imported from LDAP'). You can avoid this if you set
$LDAPSkipAutogeneratedGroup.
setup_group
Pulls the $LDAPGroupName object out of the DB or creates it if we need
to do so.
add_custom_field_value
Adds values to a Select (one|many) Custom Field. The Custom Field should
already exist, otherwise this will throw an error and not import any
data.
This could probably use some caching.
update_object_custom_field_values
Adds CF values to an object (currently only users). The Custom Field
should already exist, otherwise this will throw an error and not import
any data.
Note that this code only adds values at the moment, which on single
value CFs will remove any old value first. Multiple value CFs may behave
not quite how you expect.
import_groups import => 1|0
Takes the results of the search from "run_group_search" and maps
attributes from LDAP into "RT::Group" attributes using
$RT::LDAPGroupMapping.
Creates groups if they don't exist.
Removes users from groups if they have been removed from the group on
LDAP.
With no arguments, only prints debugging information. Pass "--import" to
actually change data.
run_group_search
Set up the appropriate arguments for a listing of users.
_import_group
The user has run us with "--import", so bring data in.
create_rt_group
Takes a hashref of args to pass to "RT::Group::Create" Will try loading
the group and will only create a new group if it can't find an existing
group with the "Name" or "EmailAddress" arg passed in.
If $LDAPUpdateOnly is true, we will not create new groups but we will
update existing ones.
There is currently no way to prevent Group data from being clobbered
from LDAP.
add_group_members
Iterate over the list of values in the "Member_Attr" LDAP entry. Look up
the appropriate username from LDAP. Add those users to the group. Remove
members of the RT Group who are no longer members of the LDAP group.
_show_group
Show debugging information about the group record we're going to import
when the groups reruns us with "--import".
disconnect_ldap
Disconnects from the LDAP server.
Takes no arguments, returns nothing.
Utility Functions
screendebug
We always log to the RT log file with level 'debug'. This duplicates the
messages to the screen.
BUGS AND LIMITATIONS
No bugs have been reported.
Please report any bugs or feature requests to
"bug-rt-extension-ldapimport@rt.cpan.org", or through the web interface
at <http://rt.cpan.org>.
AUTHOR
Kevin Falcone "<falcone@bestpractical.com>"
LICENCE AND COPYRIGHT
Copyright (c) 2007-2012, Best Practical Solutions, LLC. All rights
reserved.
This module is free software; you can redistribute it and/or modify it
under the same terms as Perl itself. See perlartistic.
DISCLAIMER OF WARRANTY
BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH
YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
NECESSARY SERVICING, REPAIR, OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENCE, BE LIABLE
TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.