|
ACTIONS from meeting
|
| |
The meeting didn't happen, but we have actions that carry!
* everyone/lloyd and ozten interested in dev engagement, talk to Christian
* benadida to look at SRP initial string email from bwarner
* JP to follow up on CEF logging with appropriate other devs.
* ST to schedule needed followup on profile proposal... more »
|
|
|
A new project for replacing passwords of different website at once
|
| |
Hi everybody, this is my first post here. I came up with idea of online password manger which allows not only automatic login to website, but also (and this is the most important part) to automatic change all or some passwords and each password will be replaced with a complex random new one, encrypted and saved to the server.... more »
|
|
|
canceling weekly
|
| |
Hi team,
The Mozilla meeting is running longer, plus we have a few people on vacation today, so let's skip the weekly meeting today.
HOWEVER, please still add updates and raise flags on the wiki:
[link]
-Ben
|
|
|
Is my use case inappropriate?
|
| |
I'm creating an application that will be used by many people with
unique accounts on a single machine with essentially no gap between
their uses (think of a university machine and application that is
shared by many students). As such, there really needs to be a way to
require users to enter their password each time. Even a short... more »
|
|
|
Dotnet 4.5
|
| |
Hopefully folks agree that I am on topic. If not, why not?
How does one make browserid real world (and fit the needs of legacy code)?
Yesterday dotnet4.5 was released - featuring commodity websso support. Sso is now officially commodity (be it the 1 billion folks with verified by visa Sso, or the webby Sso that Hallam baker started up, nearly 15 years ago (and that only now, just, "made it")).... more »
|
|
|
Registration UX Problem
|
| |
Having started some user tests on a small new system developed that uses BrowserID for authentication, I immediately got feedback from the less technically minded users that the registration process was confusing. The problem was that when they followed the link in the e-mail after registering, it opened a new, maximised browser window. This new window opens over the top of my website, so they aren't able to see that they've now been logged in. Instead they just see a new window with no way of returning to my site. Can we perhaps put the confirmation of success in the same little window as is used for the rest of the authentication process (provided that window is still open).... more »
|
|
|
Using watch()
|
| |
Any thoughts on this? I am considering pushing it into production
now, stubbed to survive the removal of .experimental. Am I crazy?
Jeff
|
|
|
new users v. new emails
|
| |
Hi all -
I am looking at the JSON payload for the KPI backend and trying to figure out how I would differentiate between some one who has no existing browserID entry, and one who has one, but is adding a new email to their persona "pool".
I suspect that I probably cannot count on the new_account field to do... more »
|
|
|
