to change the RT code to allow completely numeric user IDs? All of our
LDAP user IDs are about to change (no choice, no way of getting them to
add some letters) to numbers and RT doesn’t like this …
Originally, they were to have some letters in there but now, they won’t
…
PK
Philip Kime
NOPS Systems Architect
310 401 0407
Pretty trivial as long as they’re not stupid long.On Wed, 2007-02-21 at 11:26 -0800, Philip Kime wrote:
to change the RT code to allow completely numeric user IDs? All of our
LDAP user IDs are about to change (no choice, no way of getting them
to add some letters) to numbers and RT doesn’t like this …
Originally, they were to have some letters in there but now, they
won’t …PK
–
Philip Kime
NOPS Systems Architect
310 401 0407
List info: The rt-devel Archives
Hmm - the simplest way I can see, which I’ve done, is to check usernames
on their way in to the GUI or REST and if they are purely numeric,
prefix them with “rt”. Then the LDAP auth code strips this off to do the
auth and RT is happy. The user Load() function loads by ID if the
username is numeric and I really wouldn’t want to scour the code looking
for all possible places this sort of thing happened. Of course, this
breaks interactive authenticating to RT with an actual RT userID (as
opposed to a username) but I can’t believe anyone ever does that anyway
…
Somebody mentioned something about some scrips/templates not being happy
if the userID and email ID were not the same? But I can’t believe that -
that isn’t a problem specific to having a numeric ID and would be a real
problem if it really existed.
Somebody mentioned something about some scrips/templates not being happy
if the userID and email ID were not the same? But I can’t believe that -
that isn’t a problem specific to having a numeric ID and would be a real
problem if it really existed.
Yeah that’s definitely not the case, or we’d (and most people) be
screwed.