Cette traduction est incomplète. Aidez-nous à traduire cet article depuis l’anglais

Non standard
Cette fonctionnalité n'est ni standard, ni en voie de standardisation. Ne l'utilisez pas pour des sites accessibles sur le Web : elle ne fonctionnera pas pour tout utilisateur. Il peut également y avoir d'importantes incompatibilités entre les implémentations et son comportement peut être modifié dans le futur.

The IdentityManager of the  BrowserID protocol exposes the BrowserID API, via This API has gone through several significant revisions. Each generation is listed separately below.

The "Observer" API (Current)

The Observer API introduces much-requested features, such as an improved post-verification experience for first-time users, automatic persistent logins, and easier integration with native applications.
Registers callbacks to be invoked when a user logs into or out of a website.
Requests a signed identity assertion from the user.
Logs the user out of a website and prevents the onlogin action from automatically firing on their next visit.

Users with third-party cookies disabled may experience problems logging in using the Observer API as detailed in issue 2999.

The "Callback" API (Current)

The Callback API was introduced in November 2011. It improved upon the initial API by allowing options to be passed to and offering experimental support for BrowserID-managed persistent sessions.

Gets the user's BrowserID in a signed assertion.

The "VerifiedEmail" API (Deprecated)

The VerifiedEmail API was BrowserID's first API. It was deprecated at the end of 2011.

Gets the user's BrowserID in a signed assertion. This method is deprecated; is backwards compatible and can be used instead.