Closed Bug 51192 Opened 24 years ago Closed 21 years ago

When using LDAP, should be able to automatically create accounts for new LDAP users.

Categories

(Bugzilla :: User Accounts, enhancement, P3)

enhancement

Tracking

()

VERIFIED DUPLICATE of bug 201069

People

(Reporter: jmrobins, Assigned: myk)

References

Details

In the current LDAP patches I've submitted, when an LDAP user logs into Bugzilla 
and doesn't have a Bugzilla account, one is automatically created.  However, 
until that point, that person doesn't have an account in the Bugzilla database.  
In particular, this means that he can't be put into the CC/assigned/QA fields, 
and so on.

It would be nice to have a script that would get the information from the LDAP 
directory for new users, and create their accounts right away, so that they 
wouldn't have to log in to have things assigned to them and so on.

This would probably just be part of the contrib directory, since it's not part 
of the main functionality.  This also might not be necessary if we implement the 
enhancement in bug #51188, since we would then have access to the LDAP users 
whether or not they had Bugzilla accounts.
Blocks: 51182
This bug actually duplicates 51191.
No, the two are coming at it from opposite sides.  What this bug says is "If a 
new LDAP account is created, then create a new Bugzilla account for that user."  
What bug 51191 says is "If someone creates a new Bugzilla account, then create a 
new LDAP account for that user."
Target Milestone: --- → Future
Severity: normal → enhancement
-> Bugzilla product
Assignee: tara → myk
Component: Bugzilla → User Accounts
OS: Windows NT → All
Product: Webtools → Bugzilla
Hardware: PC → All
Version: other → unspecified
The other bug is newer, but it has a lot more discussion on it already.

*** This bug has been marked as a duplicate of 201069 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Target Milestone: Future → ---
Status: RESOLVED → VERIFIED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.