From 074785cea106179cb3305637055ab0a009ca74f2 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 8 Dec 2020 14:42:52 -0500 Subject: initial commit --- .../persona/.well-known-browserid/index.html | 61 ++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 files/pt-br/mozilla/persona/.well-known-browserid/index.html (limited to 'files/pt-br/mozilla/persona/.well-known-browserid') diff --git a/files/pt-br/mozilla/persona/.well-known-browserid/index.html b/files/pt-br/mozilla/persona/.well-known-browserid/index.html new file mode 100644 index 0000000000..9cbda7ae2b --- /dev/null +++ b/files/pt-br/mozilla/persona/.well-known-browserid/index.html @@ -0,0 +1,61 @@ +--- +title: .well-known-browserid +slug: Mozilla/Persona/.well-known-browserid +translation_of: Archive/Mozilla/Persona/.well-known-browserid +--- +

Domínios anunciam sua capacidade de atuar como Provedores de Identidade Persona (IDPs) através da publicação de um documento de apoio em /.well-known/browserid. Este documento formatado em JSON deve ser servido por HTTPS com o tipo de conteúdo application/json.

+ +

Este documento pode especificar a forma de prestação e autenticar usuários, ou pode delegar sua autoridade para outro provedor de identidade.

+ +

Nota: você também deve consultar o EspecificaçProtocolo BrowserID  como a referência técnica autorizada.

+ +

Supórte Basico

+ +

Um domínio que atua diretamente um um IDP deve fornecer três valores em seu documento de apoio:

+ + + +

Arquivo exemplo /.well-known/browserid:

+ +
{
+    "public-key": {
+        "algorithm": "RS",
+        "n": "82818905405105134410187227495885391609221288015566078542117409373192106382993306537273677557482085204736975067567111831005921322991127165013340443563713385983456311886801211241492470711576322130577278575529202840052753612576061450560588102139907846854501252327551303482213505265853706269864950437458242988327",
+        "e": "65537"
+    },
+    "authentication": "/browserid/sign_in.html",
+    "provisioning": "/browserid/provision.html"
+}
+ +

Delegated Support

+ +

HTTP redirects and other means of "moving" a /.well-known/browserid file are not permitted. If an IdP would like to delegate to another domain for authentication and provisioning, it may publish a support document which only contains an authority entry.

+ +

Example /.well-known/browserid:

+ +
{
+  "authority": "subdomain.example.com"
+}
+
+ +

Then subdomain.example.com would host its own support document, as per the example above.

+ +

The authority field is specified as a hostname plus, optionally, a port. It may not contain a path. So "example.com", "subdomain.example.com", and "subdomain.example.com:8080" are all valid, but "subdomain.example.com/login" is not.

+ +

A domain may delegate to any other domain, so long as the other domain publishes a /.well-known/browserid document.

+ +

Checklist

+ + + +

Many of these can be tested automatically with the check_primary_support script from the Persona codebase.

-- cgit v1.2.3-54-g00ecf