Identity and Authentication Systems: Difference between revisions

From Konfidi
Jump to navigationJump to search
m (Reverted edits by RicelZelri (Talk); changed back to last version by DaveBrondsema)
No edit summary
 
Line 20: Line 20:
<td>RDF URI</td>
<td>RDF URI</td>
<td>none</td>
<td>none</td>
<td>current_version + 1</td>
<td>''planned''</td>
</tr>
</tr>


Line 26: Line 26:
<td>email address</td>
<td>email address</td>
<td>SPF</td>
<td>SPF</td>
<td>current_version + 1</td>
<td>''planned''</td>
</tr>
</tr>


Line 32: Line 32:
<td>email address</td>
<td>email address</td>
<td>DKIM</td>
<td>DKIM</td>
<td>current_version + 1</td>
<td>''planned''</td>
</tr>
</tr>


Line 38: Line 38:
<td>YADIS URL</td>
<td>YADIS URL</td>
<td>OpenID</td>
<td>OpenID</td>
<td>current_version + 2</td>
<td>''planned''</td>
</tr>
</tr>



Latest revision as of 09:25, 26 January 2008

Identifiers are the "X" and the "Y" in "X trusts Y" declarations, which are stored in RDF. Authentication methods are used in a client, before querying the TrustServer to compute a trust value.

Until we have a better idea, you must PGP-sign your RDF trust declarations, so that the origin of those declarations can be verified again later by anyone. Other possibilities, like OpenID, only authenticate the session not the document, so it cannot be independently verified later.


Identifier Authentication Method Supported in Konfidi
OpenPGP fingerprint OpenPGP signature Yes
RDF URI none planned
email address SPF planned
email address DKIM planned
YADIS URL OpenID planned
YADIS URL XRI/i-names
X.509 Subject Unique Identifier X.509 Signature
JabberID ?


See also FOAF Unique Identifiers