Difference between revisions of "Authority"

From IDESG Wiki
Jump to: navigation, search
m (17 revisions imported: Initial Upload of old pages from IDESG Wiki)
 
(11 intermediate revisions by one other user not shown)
Line 12: Line 12:
 
== Status ==
 
== Status ==
 
<span style="background: yellow">Proposed</span>
 
<span style="background: yellow">Proposed</span>
 
  
 
== Disambiguation ==
 
== Disambiguation ==
* A natural or legal
+
Authority for the IDESG applies to any site that asserts its identity with a private key. The term call also be used with respect to a [[Relying Party]] or an [[Identity Provider]], or even a [[Identity Ecosystem Framework]] network.
 +
 
 
=== Same term, different concept? ===
 
=== Same term, different concept? ===
* [[
+
*A [https://wiki.idesg.org/wiki/index.php?title=Definitions#Certificate_Authority Certificate Authority] issues (usually X.509) public key certificates.
 +
*An [https://tools.ietf.org/html/rfc3986#section-3.2 HTTP Authority] is a common  means for distinguishing an authority based on a registered name or server address, along with optional port and user information (username:password@somesite.com:8080).
  
 
=== Different term, same concept? ===
 
=== Different term, same concept? ===

Latest revision as of 03:00, 28 June 2018

Proposed Definition

  1. A trusted entity that issues and revokes trusted information, including credentials and attribute assertion.
  2. A trusted entity that creates, issues, maintains and revokes trusted information, including credentials and attributes. (D'Agostino, Krum)

Notes

TBD

Sources

NIST 800-63

Status

Proposed

Disambiguation

Authority for the IDESG applies to any site that asserts its identity with a private key. The term call also be used with respect to a Relying Party or an Identity Provider, or even a Identity Ecosystem Framework network.

Same term, different concept?

  • A Certificate Authority issues (usually X.509) public key certificates.
  • An HTTP Authority is a common means for distinguishing an authority based on a registered name or server address, along with optional port and user information (username:password@somesite.com:8080).

Different term, same concept?



Quick Links: Taxonomy | Taxonomy Project Management | Taxonomy AHG Catalog | Taxonomy AHG Glossary |