Search results
Jump to navigation
Jump to search
Page title matches
- #REDIRECT [[Four Party Authentication and Authorization Use Case]]66 bytes (8 words) - 03:58, 28 June 2018
- Four Party Authentication and Authorization ...iders. The most robust example in the document is referred to as the Four Party model due to the number of actors involved in the process. It describes a7 KB (1,007 words) - 03:58, 28 June 2018
- ...while still providing access to a [[User Object]] that is held by another party. It forms the majority of [[Trusted Entity|Trusted Entities]] and is often ...d in the [[Identity Model]]. This paper describes the case where the third party fully accepts the fiduciary responsibility to hide the user's real-world id4 KB (626 words) - 21:21, 14 May 2020
- Patient authenticates to a trusted third party to access Electronic Health Records (EHR) at one provider and extract recor #Trusted third party that will authenticate a user to the IAL2 requirements of the [[Health Care5 KB (842 words) - 03:00, 21 May 2019
- #REDIRECT [[Patient uses Trusted Third Party to authenticate and move EHR]]75 bytes (11 words) - 02:59, 21 May 2019
Page text matches
- This page is designed to assist designers and developers of relying party (RP) web sites. Technical terms are used to convey the information that the ...goals set out the needs and constraints on an example for use by a Relying Party (RP) systems design.24 KB (3,980 words) - 19:57, 13 November 2020
- ...] electronic credentials to subscribers. A CSP may be an independent third party or [it may] issue credentials for its own use. ...s electronic credentials to subscribers. A CSP may be an independent third party or issue credentials for its own use. ([https://nvlpubs.nist.gov/nistpubs/S3 KB (467 words) - 01:56, 15 May 2020
- ...in the possession of the user. This case extends that to allow the relying party to specifically request an integrity claim from the user's device. ...horized users. This is not possible if the resource owner (aka the relying party) does not trust the user's device's integrity with respect to confidential12 KB (1,835 words) - 20:44, 5 November 2020
- ...in categories of Digital Entity: (1) the [[User Agent]], (2) the [[Relying Party]] and (3) the [[Identity Provider]].719 bytes (90 words) - 17:03, 7 November 2018
- ...cture]], [[Registration Authority]], [[Re-key (a Certificate)]], [[Relying Party]], [[Renew (a Certificate)]], [[Repository]], [[Responsible Individual]], [4 KB (377 words) - 22:59, 18 February 2021
- '''Category''': Relying Party Policy ...]], [[Pseudonym]], [[Registration]], [[Registration Authority]], [[Relying Party]], [[Salt]], [[Sensitive Information]], [[Shared Secret]], [[Strong Man In3 KB (373 words) - 23:01, 18 February 2021
- ##USE Case Gap Analysis with 4-party Authentication #Use Case 4-party Authentication & Authorization Template (Excel), 3 tabs5 KB (796 words) - 03:58, 28 June 2018
- ...ow that we are not in sync. UXC has not yet added a definition for relying party. Suggestion was to add it with the glossary attached. Paul Knight thought ...ut the identity of an individual or authentication assertions from another party such as an Identity Provider, Credential Service Provider (CSP), or Trusted4 KB (682 words) - 03:58, 28 June 2018
- ...g, we should make as much progress as possible. If you have a responsible party who wants to self-assess, that they will be accountable for, then we need t5 KB (766 words) - 03:58, 28 June 2018
- ##4-party Authentication | 11 || Four Party Authentication and Authorization Use Case || Ryan Galluzzo3 KB (408 words) - 03:58, 28 June 2018
- ...laces. Define users: UXC users are end user – human users – in a relying party – or somewhere else. We are addressing human users. That is probably so7 KB (1,070 words) - 03:58, 28 June 2018
- * Relying party (RP) in this case is a specific internet connection web site, not always pa ...ontractual obligations made by the user are often important to the relying party.3 KB (429 words) - 23:13, 20 May 2020
- #REDIRECT [[Four Party Authentication and Authorization Use Case]]66 bytes (8 words) - 03:58, 28 June 2018
- Four Party Authentication and Authorization ...iders. The most robust example in the document is referred to as the Four Party model due to the number of actors involved in the process. It describes a7 KB (1,007 words) - 03:58, 28 June 2018
- ...ity requirements in a common framework. It would be possible for a relying party or user to list the affinity groups (frameworks) that they could support to ##Relying party (RP called a user client in OAuth; NIST = An entity that relies upon the su8 KB (1,315 words) - 19:29, 30 July 2020
- ...shed rules and specific rights or authority associated with the requesting party ...shed rules and specific rights or authority associated with the requesting party.845 KB (86,833 words) - 04:00, 28 June 2018
- those third-party packaged applications that have their own built-in authentication that is n A statement from a verifier to a relying party that contains identity information about a subscriber. Assertions may also135 KB (15,051 words) - 04:00, 28 June 2018
- ...blish a user’s identity with an Identity Provider (IdP) role and a Relying Party (RP) role. This case is specifically designed to include general security, ...om providers for a limited validity period and provide them to the relying party using a policy provided by the user.5 KB (810 words) - 04:00, 28 June 2018
- ...at the user needs to sign on with an identity that is known to the Relying party. Users need to be known to the relying party web site in order to have a full experience on the site. Typically most con10 KB (1,596 words) - 20:11, 15 October 2019
- ...infer the entity involved nor is such data sufficient to permit a relying party to associate multiple interactions with the entity. ...to infer the entity involved and for which information to permit a relying party to associate multiple interactions with the entity’s claimed identity is11 KB (1,758 words) - 04:00, 28 June 2018