173330 - offer to use a central bugzilla user database or authentication service

Status: RESOLVED WONTFIX

(Bugzilla :: Bugzilla-General, enhancement)

Description

[blitzreiter]

Meanwhile many programs use bugzilla as a bugtracking environment, 
unfortunately you have to register your account to all this services seperately.

Wouldnt it be great to have a kind of Bugzilla PASSPORT service. 

Or a real Mozilla Bucktracking server that can be used for bugtracking of many 
freee projects (similar to sourceforge...) so you just have to register "once". 
When you are looking for a sponsor of such a big project, I think the German 
Government would pay for it. They are going to create a kind of OSS Foundation 
that does open-projects-assistence, and found projects like this, take 
www.berlios.org as an example.

Comment 1

[Ricky Ng-Adam]

Instead of centralizing, why not keep the Bugzilla separate and use "trust"
between servers to create the accounts?

For example, 

-You register to a Linux distribution Bugzilla (most likely entry point), your
email is authenticated and your user created
-You decide to move a bug UPSTREAM (probably the most frequent way you'll need
to have another account) - see #123130
-You choose the upstream project from a list of "friendly" Bugzilla peers (KDE,
GNOME, Mozilla, etc).
-The account information is submitted, encrypted with a private key and
decrypted by the peer Bugzilla by the originating Bugzilla public key

I think the question is - the account information, will it be a copy or a
reference back to the originating Bugzilla?

Comment 2

[Dave Miller [:justdave]]

*** Bug 260486 has been marked as a duplicate of this bug. ***

Comment 3

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 4

[Dylan Hardison [:dylan] (he/him)]

This is too big in scope and will never be done.

We have a pluggable auth system and also support for sending API keys between installations.