Difference between revisions of "Verified Claim"

From MgmtWiki
Jump to: navigation, search
(→‎References)
(→‎Solution)
Line 16: Line 16:
 
# The [[Web Site]] will evaluate the [[Verified Claim]]s and determine whether to authorize access to the resource.
 
# The [[Web Site]] will evaluate the [[Verified Claim]]s and determine whether to authorize access to the resource.
 
# Optionally the [[Web Site]] will request additional claims to meet the needs to authorize access.
 
# Optionally the [[Web Site]] will request additional claims to meet the needs to authorize access.
−
 
−
 
  
 
* In computer networking a variety of statements can be made by a user to acquire authorized access to a resource.
 
* In computer networking a variety of statements can be made by a user to acquire authorized access to a resource.
 
* The distinction as to [[Authentication]], who a user is, versus [[Authorization]], or what that user is permitted to do, is no longer helpful.
 
* The distinction as to [[Authentication]], who a user is, versus [[Authorization]], or what that user is permitted to do, is no longer helpful.
−
* NIST has recognized that there are multiple metrics for the quality of statements about a user in their third update to SP 800-63
+
* NIST has recognized that there are multiple metrics for the [[Assurance]] of statements about a user in their third update to SP 800-63-B
−
* [[Claim]]s can be highly detailed, do to data fields, or a collection of fields, like the [[User]] address, this can be overwhelming if presented for [[User Consent]]. Some protocols, like [[OpenID Connect]] provide for aggregated collections of claims that OpenID calls '''[[Scope]]'''.<ref>Nat Sakimura ''Scopes and Claims in OpenID Connect'' https://nat.sakimura.org/2012/01/26/scopes-and-claims-in-openid-connect/</ref>
 
  
 
==References==
 
==References==

Revision as of 20:43, 1 November 2019

Full Title or Meme

A statement (or collection of data) by or about a Subject is a claim. If there is some corroboration of the claim, it is called a Validated or Verified Claim.

Context

  • Any site can host data about a Subject and even offer to sell that data to others. Several problems are assciated with that exchange:
  1. The data may be false through negligence, incompetence or out-right fraud.
  2. The site that contains the data may have no right to share that data with others.
  3. A claim represents a data item without much context. Adding context to that data can create Verified Information which can have great value.

Solution

Claims typically go through a series of steps, for example:

  1. A User will go to a Web Site hosting a Resource that the user wants to access.
  2. The Web Site will send a scope to a User asking for Claims to authorize access.
  3. The User Agent should know, a priori, where to send the Claims for verification.
  4. The Verified Claims will be collected and forwarded to the Web Site.
  5. The Web Site will evaluate the Verified Claims and determine whether to authorize access to the resource.
  6. Optionally the Web Site will request additional claims to meet the needs to authorize access.
  • In computer networking a variety of statements can be made by a user to acquire authorized access to a resource.
  • The distinction as to Authentication, who a user is, versus Authorization, or what that user is permitted to do, is no longer helpful.
  • NIST has recognized that there are multiple metrics for the Assurance of statements about a user in their third update to SP 800-63-B

References

Retrieved from "http://tcwiki.azurewebsites.net/index.php?title=Verified_Claim&oldid=6790"