Skip to content
Browse files

add links for browserid primaries post

  • Loading branch information...
1 parent 66be9f7 commit 65be3a1895a9acab295cc2a25a25ec3f8cae518e @lloyd committed Oct 19, 2011
Showing with 39 additions and 3 deletions.
  1. +20 −2 feed.atom
  2. +1 −0 links/primary-identity-authorities-in-browserid.md
  3. +18 −1 posts/summary.html
View
22 feed.atom
@@ -4,12 +4,30 @@
<title>lloyd.io - Lloyd's blog</title>
<link href="http://lloyd.io" rel="alternate" />
<link type="application/atom+xml" rel="self" href="http://lloyd.io/feed.atom"/>
- <updated>2011-08-01T19:38:02Z</updated>
+ <updated>2011-10-19T20:58:53Z</updated>
<author>
<name>Lloyd Hilaiel</name>
<email>lloyd@hilaiel.com</email>
</author>
<entry>
+ <title type="html">Primary Identity Authorities in BrowserID</title>
+ <link href="http://lloyd.io/primary-identity-authorities-in-browserid"/>
+ <id>http://lloyd.io/primary-identity-authorities-in-browserid</id>
+ <updated>2011-10-17T06:00:00Z</updated>
+ <summary type="html">&lt;p&gt;BrowserID is designed to be a distributed authentication system.
+Once fully deployed there will be no central servers required for the
+system to function, and the process of authenticating to a website will
+require minimal live communication between the user's browser, the
+identity provider (IdP), and the website being logged into. In order to
+achieve this, two things are required:&lt;/p&gt;
+&lt;ol&gt;
+&lt;li&gt;Browser vendors must build native support for BrowserID into their products.&lt;/li&gt;
+&lt;li&gt;IdP's must build BrowserID support to vouch for their users ownership of issued email addresses.&lt;/li&gt;
+&lt;/ol&gt;
+&lt;p&gt;This post addresses #2, proposing precisely what &lt;em&gt;BrowserID Support&lt;/em&gt; means
+for an IdP, and how it works.&lt;/p&gt;</summary>
+ </entry>
+ <entry>
<title type="html">Applying Gitflow</title>
<link href="http://lloyd.io/applying-gitflow"/>
<id>http://lloyd.io/applying-gitflow</id>
@@ -20,7 +38,7 @@ BrowserID project, which is based on
The &lt;a href="https://browserid.org"&gt;BrowserID&lt;/a&gt; project has recently become a
high visibility venture, with many sites actively using the service
for authentication. This overnight change from experiment to
-production service presents us with a dilemma: the project is still in
+production presents us with a dilemma: the project is still in
early stages and needs to be able to rapidly iterate and evolve, but
at the same time it must be stable and available for those who have
started using it. This post describes how we'll resolve this dilemma.&lt;/p&gt;</summary>
View
1 links/primary-identity-authorities-in-browserid.md
View
19 posts/summary.html
@@ -1,3 +1,20 @@
+<div class="post" filename="2011-10-17-primary-identity-authorities-in-browserid.md" shortname="primary-identity-authorities-in-browserid" format="markdown">
+ <div class="title"><a href="/primary-identity-authorities-in-browserid">Primary Identity Authorities in BrowserID</a></div>
+ <div class="date">2011-10-17</div>
+ <div class="comments"><a href="/primary-identity-authorities-in-browserid#disqus_thread" data-disqus-identifier="primary-identity-authorities-in-browserid">comments</a></div>
+ <div class="abstract"><p>BrowserID is designed to be a distributed authentication system.
+Once fully deployed there will be no central servers required for the
+system to function, and the process of authenticating to a website will
+require minimal live communication between the user's browser, the
+identity provider (IdP), and the website being logged into. In order to
+achieve this, two things are required:</p>
+<ol>
+<li>Browser vendors must build native support for BrowserID into their products.</li>
+<li>IdP's must build BrowserID support to vouch for their users ownership of issued email addresses.</li>
+</ol>
+<p>This post addresses #2, proposing precisely what <em>BrowserID Support</em> means
+for an IdP, and how it works.</p></div>
+</div>
<div class="post" filename="2011-08-01-applying-gitflow.md" shortname="applying-gitflow" format="markdown">
<div class="title"><a href="/applying-gitflow">Applying Gitflow</a></div>
<div class="date">2011-08-01</div>
@@ -8,7 +25,7 @@
The <a href="https://browserid.org">BrowserID</a> project has recently become a
high visibility venture, with many sites actively using the service
for authentication. This overnight change from experiment to
-production service presents us with a dilemma: the project is still in
+production presents us with a dilemma: the project is still in
early stages and needs to be able to rapidly iterate and evolve, but
at the same time it must be stable and available for those who have
started using it. This post describes how we'll resolve this dilemma.</p></div>

0 comments on commit 65be3a1

Please sign in to comment.
Something went wrong with that request. Please try again.