Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

1password HTTP Authentication

  • 1 èsì
  • 3 ní àwọn ìṣòro yìí
  • 3 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ the-edmeister

more options

This question has been beat to death on 1password's forums, but I wanted to get some exposure here, since the bottle neck seems to be on Mozilla's side (as mentioned from 1password developers).

As you may or may not know, 1password is now relying on the Jetpack API for it's Firefox extension. This is good because 1password developers won't have to develop a new extension each time FF updates. BUT... this also means that 1password does not have access to the http authentication prompt window which worked very very well before the whole Jetpack migration.

Mozilla developers, when can we see an update to the API which will allow plugins, such as 1password to work with the http auth window?

http://help.agilebits.com/1Password3/http_auth.html

This question has been beat to death on 1password's forums, but I wanted to get some exposure here, since the bottle neck seems to be on Mozilla's side (as mentioned from 1password developers). As you may or may not know, 1password is now relying on the Jetpack API for it's Firefox extension. This is good because 1password developers won't have to develop a new extension each time FF updates. BUT... this also means that 1password does not have access to the http authentication prompt window which worked very very well before the whole Jetpack migration. Mozilla developers, when can we see an update to the API which will allow plugins, such as 1password to work with the http auth window? http://help.agilebits.com/1Password3/http_auth.html

All Replies (1)

more options

Sorry, the Mozilla developers rarely visit this forum. If Agilebits has a problem with the Jetpack API and feel it needs to be fixed, the proper venue for them (or anyone, for that matter) is to file a Bug report at Bugzilla.Mozilla.Org . If they have a patch to fix the issue, they can include the patch with the report.

That said, there is another forum for Add-on support which would be more in line with development issues related to Jetpack API's.