Closed
Bug 698798
Opened 14 years ago
Closed 14 years ago
Deploy BrowserID extension to staging server
Categories
(bugzilla.mozilla.org :: Extensions, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: gerv, Assigned: dkl)
Details
It might be good, to aid the security review, to deploy the BrowserID extension to the BMO staging server. I guess this would mean checking it into bmo-4.0 with a "disabled" file, and then removing that file on the staging server.
Gerv
Reporter | ||
Comment 2•14 years ago
|
||
Ah, I didn't realise it had its own branch. I was certainly thinking of bugzilla-stage-tip.
Gerv
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•14 years ago
|
||
Should be on https://bugzilla-stage-tip.mozilla.org shortly.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•14 years ago
|
||
Hi dkl,
I don't see this on b-s-t. Is that because I forgot to mention that you also need to check in the patch from bug 698418 with the two hooks? :-)
Gerv
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 5•14 years ago
|
||
(In reply to Gervase Markham [:gerv] from comment #4)
> Hi dkl,
>
> I don't see this on b-s-t. Is that because I forgot to mention that you also
> need to check in the patch from bug 698418 with the two hooks? :-)
>
> Gerv
Sorry took so long to get back to this. The data/params were not set on b-s-t to allow BrowserID,CGI login stack and was still set to CGI. The SignIn icon now displays but it is giving me "invalid username/password" error when signing in using BrowserID. I will need to to investigate further why it is not recognizing my data from the browserid server. You could try yours and see if it works.
dkl
Reporter | ||
Comment 6•14 years ago
|
||
I get the same. Our accounts are too powerful. Update to the latest code and it'll produce a custom error which makes this more clear. I successfully logged in using a low-privilege account.
Gerv
Assignee | ||
Comment 7•14 years ago
|
||
(In reply to Gervase Markham [:gerv] from comment #6)
> I get the same. Our accounts are too powerful. Update to the latest code and
> it'll produce a custom error which makes this more clear. I successfully
> logged in using a low-privilege account.
>
> Gerv
Ah right. Good catch. Forgot about the part about group permissions. Ok, so at least we
know it is working :)
Dkl
Assignee | ||
Comment 8•14 years ago
|
||
Ok, so we can close this now since it is working as designed.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 9•14 years ago
|
||
You need to update to the latest code, though :-)
Gerv
Assignee | ||
Comment 10•14 years ago
|
||
(In reply to Gervase Markham [:gerv] from comment #9)
> You need to update to the latest code, though :-)
>
> Gerv
Ok. Updated and should show up on b-s-t sortly.
dkl
Updated•6 years ago
|
Component: Extensions: Other → Extensions
You need to log in
before you can comment on or make changes to this bug.
Description
•