• Skip to main content
  • Select language
  • Skip to search
MDN Web Docs
  • Technologies
    • HTML
    • CSS
    • JavaScript
    • Graphics
    • HTTP
    • APIs / DOM
    • WebExtensions
    • MathML
  • References & Guides
    • Learn web development
    • Tutorials
    • References
    • Developer Guides
    • Accessibility
    • Game development
    • ...more docs
Add-ons
  1. MDN
  2. Mozilla
  3. Add-ons
  4. Add-on SDK
  5. High-Level APIs
  6. passwords

passwords

In This Article
  1. Usage
    1. Credentials
      1. Add-on Credential
      2. HTML Form Credential
      3. HTTP Authentication Credential
    2. onComplete and onError
  2. Globals
    1. Functions
      1. search(options)
      2. store(options)
      3. remove(options)

Add-ons using the techniques described in this document are considered a legacy technology in Firefox. Don't use these techniques to develop new add-ons. Use WebExtensions instead. If you maintain an add-on which uses the techniques described here, consider migrating it to use WebExtensions.

From Firefox 53 onwards, no new legacy add-ons will be accepted on addons.mozilla.org (AMO).

From Firefox 57 onwards, WebExtensions will be the only supported extension type, and Firefox will not load other types.

Even before Firefox 57, changes coming up in the Firefox platform will break many legacy extensions. These changes include multiprocess Firefox (e10s), sandboxing, and multiple content processes. Legacy extensions that are affected by these changes should migrate to WebExtensions if they can. See the "Compatibility Milestones" document for more.

A wiki page containing resources, migration paths, office hours, and more, is available to help developers transition to the new technologies.

Stable

Interact with Firefox's Password Manager to add, retrieve and remove stored credentials.

Usage

A credential is the set of information a user supplies to authenticate herself with a service. Typically a credential consists of a username and a password.

Using this module you can:

  1. Search for credentials which have been stored in the Password Manager. You can then use the credentials to access their related service (for example, by logging into a web site).

  2. Store credentials in the Password Manager. You can store different sorts of credentials, as outlined in the "Credentials" section below.

  3. Remove stored credentials from the Password Manager.

Credentials

In this API, credentials are represented by objects.

You create credential objects to pass into the API, and the API also returns credential objects to you. The sections below explain both the properties you should define on credential objects and the properties you can expect on credential objects returned by the API.

All credential objects include username and password properties. Different sorts of stored credentials include various additional properties, as outlined in this section.

You can use the Passwords API with three sorts of credentials:

  • Add-on credentials
  • HTML form credentials
  • HTTP Authentication credentials

Add-on Credential

These are associated with your add-on rather than a particular web site. They contain the following properties:

username The username.
password The password.
url

For an add-on credential, this property is of the form:
addon:<addon-id>, where <addon-id> is the add-on's Program ID.

You don't supply this value when storing an add-on credential: it is automatically generated for you. However, you can use it to work out which stored credentials belong to your add-on by comparing it with the uri property of the self module.

realm

You can use this as a name for the credential, to distinguish it from any other credentials you've stored.

The realm is displayed in Firefox's Password Manager, under "Site", in brackets after the URL. For example, if the realm for a credential is "User Registration", then its "Site" field will look something like:

addon:jid0-01mBBFyu0ZAXCFuB1JYKooSTKIc (User Registration)

HTML Form Credential

If a web service uses HTML forms to authenticate its users, then the corresponding credential is an HTML Form credential.

It contains the following properties:

username The username.
password The password.
url The URL for the web service which requires the credential. You should omit anything after the hostname and (optional) port.
formSubmitURL The value of the form's "action" attribute. You should omit anything after the hostname and (optional) port. If the form doesn't contain an "action" attribute, this property should match the url property.
usernameField The value of the "name" attribute for the form's username field.
passwordField The value of the "name" attribute for the form's password field.

So: given a form at http://www.example.com/login with the following HTML:

<form action="http://login.example.com/foo/authenticate.cgi">
      <div>Please log in.</div>
      <label>Username:</label> <input type="text" name="uname">
      <label>Password:</label> <input type="password" name="pword">
</form>

The corresponding values for the credential (excluding username and password) should be:

  url: "http://www.example.com"
  formSubmitURL: "http://login.example.com"
  usernameField: "uname"
  passwordField: "pword"

Note that for both url and formSubmitURL, the portion of the URL after the hostname is omitted.

HTTP Authentication Credential

These are used to authenticate the user to a web site which uses HTTP Authentication, as detailed in RFC 2617. They contain the following properties:

username The username.
password The password.
url The URL for the web service which requires the credential. You should omit anything after the hostname and (optional) port.
realm

The WWW-Authenticate response header sent by the server may include a "realm" field as detailed in RFC 2617. If it does, this property contains the value for the "realm" field. Otherwise, it is omitted.

The realm is displayed in Firefox's Password Manager, under "Site", in brackets after the URL.

So: if a web server at http://www.example.com requested authentication with a response code like this:

  HTTP/1.0 401 Authorization Required
  Server: Apache/1.3.27
  WWW-Authenticate: Basic realm="ExampleCo Login"

The corresponding values for the credential (excluding username and password) should be:

  url: "http://www.example.com"
  realm: "ExampleCo Login"

onComplete and onError

This API is explicitly asynchronous, so all its functions take two callback functions as additional options: onComplete and onError.

onComplete is called when the operation has completed successfully and onError is called when the function encounters an error.

Because the search function is expected to return a list of matching credentials, its onComplete option is mandatory. Because the other functions don't return a value in case of success their onComplete options are optional.

For all functions, onError is optional.

Globals

Functions

search(options)

This function is used to retrieve a credential, or a list of credentials, stored in the Password Manager.

You pass it any subset of the possible properties a credential can contain. Credentials which match all the properties you supplied are returned as an argument to the onComplete callback.

So if you pass in an empty set of properties, all stored credentials are returned:

function show_all_passwords() {
  require("sdk/passwords").search({
    onComplete: function onComplete(credentials) {
      credentials.forEach(function(credential) {
        console.log(credential.username);
        console.log(credential.password);
        });
      }
    });
  }

If you pass it a single property, only credentials matching that property are returned:

function show_passwords_for_joe() {
  require("sdk/passwords").search({
    username: "joe",
    onComplete: function onComplete(credentials) {
      credentials.forEach(function(credential) {
        console.log(credential.username);
        console.log(credential.password);
        });
      }
    });
  }

If you pass more than one property, returned credentials must match all of them:

function show_google_password_for_joe() {
  require("sdk/passwords").search({
    username: "joe",
    url: "https://www.google.com",
    onComplete: function onComplete(credentials) {
      credentials.forEach(function(credential) {
        console.log(credential.username);
        console.log(credential.password);
        });
      }
    });
  }

To retrieve only credentials associated with your add-on, use the url property, initialized from self.uri:

function show_my_addon_passwords() {
  require("sdk/passwords").search({
    url: require("sdk/self").uri,
    onComplete: function onComplete(credentials) {
      credentials.forEach(function(credential) {
        console.log(credential.username);
        console.log(credential.password);
        });
      }
    });
  }
Parameters

options : object
Required options:

Name Type  
onComplete function

The callback function that is called once the function completes successfully. It is passed all the matching credentials as a list. This is the only mandatory option.

Optional options:

Name Type  
username string

The username for the credential.

password string

The password for the credential.

url string

The URL associated with the credential.

formSubmitURL string

The URL an HTML form credential is submitted to.

realm string

For HTTP Authentication credentials, the realm for which the credential was requested. For add-on credentials, a name for the credential.

usernameField string

The value of the name attribute for the user name input field in a form.

passwordField string

The value of the name attribute for the password input field in a form.

onError function

The callback function that is called if the function failed. The callback is passed an error containing a reason of a failure: this is an nsIException object.

store(options)

This function is used to store a credential in the Password Manager.

It takes an options object as an argument: this contains all the properties for the new credential.

As different sorts of credentials contain different properties, the appropriate options differ depending on the sort of credential being stored.

To store an add-on credential:

require("sdk/passwords").store({
  realm: "User Registration",
  username: "joe",
  password: "SeCrEt123",
});

To store an HTML form credential:

require("sdk/passwords").store({
  url: "http://www.example.com",
  formSubmitURL: "http://login.example.com",
  username: "joe",
  usernameField: "uname",
  password: "SeCrEt123",
  passwordField: "pword"
});

To store an HTTP Authentication credential:

require("sdk/passwords").store({
  url: "http://www.example.com",
  realm: "ExampleCo Login",
  username: "joe",
  password: "SeCrEt123",
});

See "Credentials" above for more details on how to set these properties.

The options parameter may also include onComplete and onError callback functions, which are called when the function has completed successfully and when it encounters an error, respectively. These options are both optional.

Parameters

options : object
Required options:

Name Type  
username string

The username for the credential.

password string

The password for the credential.

Optional options:

Name Type  
url string

The URL to which the credential applies. Omitted for add-on credentials.

formSubmitURL string

The URL a form-based credential was submitted to. Omitted for add-on credentials and HTTP Authentication credentials.

realm string

For HTTP Authentication credentials, the realm for which the credential was requested. For add-on credentials, a name for the credential.

usernameField string

The value of the name attribute for the username input in a form. Omitted for add-on credentials and HTTP Authentication credentials.

passwordField string

The value of the name attribute for the password input in a form. Omitted for add-on credentials and HTTP Authentication credentials.

onComplete function

The callback function that is called once the function completes successfully.

onError function

The callback function that is called if the function failed. The callback is passed an error argument: this is an nsIException object.

remove(options)

Removes a stored credential. You supply it all the properties of the credential to remove, along with optional onComplete and onError callbacks.

Because you must supply all the credential's properties, it may be convenient to call search first, and use its output as the input to remove. For example, to remove all of joe's stored credentials:

require("sdk/passwords").search({
  username: "joe",
  onComplete: function onComplete(credentials) {
    credentials.forEach(require("sdk/passwords").remove);
  })
});

To change an existing credential just call store after remove succeeds:

require("sdk/passwords").remove({
  realm: "User Registration",
  username: "joe",
  password: "SeCrEt123"
  onComplete: function onComplete() {
    require("sdk/passwords").store({
      realm: "User Registration",
      username: "joe",
      password: "{new password}"
    })
  }
});
Parameters

options : object
Required options:

Name Type  
username string

The username for the credential.

password string

The password for the credential.

Optional options:

Name Type  
url string

The URL to which the credential applies. Omitted for add-on credentials.

formSubmitURL string

The URL a form-based credential was submitted to. Omitted for add-on credentials and HTTP Authentication credentials.

realm string

For HTTP Authentication credentials, the realm for which the credential was requested. For add-on credentials, a name for the credential.

usernameField string

The value of the name attribute for the username input in a form. Omitted for add-on credentials and HTTP Authentication credentials.

passwordField string

The value of the name attribute for the password input in a form. Omitted for add-on credentials and HTTP Authentication credentials.

onComplete function

The callback function that is called once the function has completed successfully.

onError function

The callback function that is called if the function failed. The callback is passed an error argument: this is an nsIException object.

 

Document Tags and Contributors

Tags: 
  • Add-on SDK
 Contributors to this page: wbamberg
 Last updated by: wbamberg, Dec 1, 2016, 10:22:51 AM
See also
  1. WebExtensions
  2. Getting started
    1. What are WebExtensions?
    2. Your first WebExtension
    3. Your second WebExtension
    4. Anatomy of a WebExtension
    5. Example WebExtensions
  3. How to
    1. Intercept HTTP requests
    2. Modify a web page
    3. Add a button to the toolbar
    4. Implement a settings page
  4. Concepts
    1. Using the JavaScript APIs
    2. User interface components
    3. Content scripts
    4. Match patterns
    5. Internationalization
    6. Content Security Policy
    7. Native messaging
  5. Porting
    1. Porting a Google Chrome extension
    2. Porting a legacy Firefox add-on
    3. Embedded WebExtensions
    4. Comparison with the Add-on SDK
    5. Comparison with XUL/XPCOM extensions
    6. Chrome incompatibilities
  6. Firefox workflow
    1. Temporary Installation in Firefox
    2. Debugging
    3. Getting started with web-ext
    4. web-ext command reference
    5. WebExtensions and the Add-on ID
    6. Publishing your WebExtension
  7. JavaScript APIs
    1. Browser support for JavaScript APIs
    2. alarms
    3. bookmarks
    4. browserAction
    5. browsingData
    6. commands
    7. contextMenus
    8. contextualIdentities
    9. cookies
    10. downloads
    11. events
    12. extension
    13. extensionTypes
    14. history
    15. i18n
    16. identity
    17. idle
    18. management
    19. notifications
    20. omnibox
    21. pageAction
    22. runtime
    23. sessions
    24. sidebarAction
    25. storage
    26. tabs
    27. topSites
    28. webNavigation
    29. webRequest
    30. windows
  8. Manifest keys
    1. applications
    2. author
    3. background
    4. browser_action
    5. chrome_url_overrides
    6. commands
    7. content_scripts
    8. content_security_policy
    9. default_locale
    10. description
    11. developer
    12. homepage_url
    13. icons
    14. manifest_version
    15. name
    16. omnibox
    17. options_ui
    18. page_action
    19. permissions
    20. short_name
    21. sidebar_action
    22. version
    23. web_accessible_resources
  9. Add-on SDK
  10. Getting started
    1. Installation
    2. Getting started
    3. Troubleshooting
  11. High-Level APIs
    1. addon-page
    2. base64
    3. clipboard
    4. context-menu
    5. hotkeys
    6. indexed-db
    7. l10n
    8. notifications
    9. page-mod
    10. page-worker
    11. panel
    12. passwords
    13. private-browsing
    14. querystring
    15. request
    16. selection
    17. self
    18. simple-prefs
    19. simple-storage
    20. system
    21. tabs
    22. timers
    23. ui
    24. url
    25. webextension
    26. widget
    27. windows
  12. Low-Level APIs
    1. /loader
    2. chrome
    3. console/plain-text
    4. console/traceback
    5. content/content
    6. content/loader
    7. content/mod
    8. content/symbiont
    9. content/worker
    10. core/heritage
    11. core/namespace
    12. core/promise
    13. dev/panel
    14. event/core
    15. event/target
    16. frame/hidden-frame
    17. frame/utils
    18. fs/path
    19. io/byte-streams
    20. io/file
    21. io/text-streams
    22. lang/functional
    23. lang/type
    24. loader/cuddlefish
    25. loader/sandbox
    26. net/url
    27. net/xhr
    28. places/bookmarks
    29. places/favicon
    30. places/history
    31. platform/xpcom
    32. preferences/event-target
    33. preferences/service
    34. remote/child
    35. remote/parent
    36. stylesheet/style
    37. stylesheet/utils
    38. system/child_process
    39. system/environment
    40. system/events
    41. system/runtime
    42. system/unload
    43. system/xul-app
    44. tabs/utils
    45. test/assert
    46. test/harness
    47. test/httpd
    48. test/runner
    49. test/utils
    50. ui/button/action
    51. ui/button/toggle
    52. ui/frame
    53. ui/id
    54. ui/sidebar
    55. ui/toolbar
    56. util/array
    57. util/collection
    58. util/deprecate
    59. util/list
    60. util/match-pattern
    61. util/object
    62. util/uuid
    63. window/utils
  13. Firefox for Android
  14. Getting started
    1. Walkthrough
    2. Debugging
    3. Code snippets
  15. APIs
    1. Accounts.jsm
    2. BrowserApp
    3. HelperApps.jsm
    4. Home.jsm
    5. HomeProvider.jsm
    6. JavaAddonManager.jsm
    7. NativeWindow
    8. Notifications.jsm
    9. PageActions.jsm
    10. Prompt.jsm
    11. RuntimePermissions.jsm
    12. Snackbars.jsm
    13. Sound.jsm
    14. Tab
  16. Legacy
  17. Restartless extensions
    1. Overview
  18. Overlay extensions
    1. Overview
  19. Themes
  20. Lightweight themes
    1. Overview
  21. Complete themes
    1. Overview
  22. Publishing add-ons
  23. Guides
    1. Signing and distribution overview
    2. Submit an add-on
    3. Review policies
    4. Developer agreement
    5. Featured add-ons
    6. Contact addons.mozilla.org
  24. Community and support
  25. Channels
    1. Add-ons blog
    2. Add-on forums
    3. Stack Overflow
    4. Development newsgroup
    5. IRC Channel