Relying Party

Overview#

Relying Party (RP) is a system entity that decides to take an action based on information from another Entity.

Examples#

In SAML Relying Party depends on receiving assertions from an asserting party (a SAML authority) about a Digital Subject.

An OAuth Client that supports OpenID Connect is also called a Relying Party because it relies on the OpenID Connect Provider to assert the user’s Digital Identity.

Relying Party (RP) Application#

When you build an application that relies on claims, you are building a Relying Party (RP) application. Synonyms for an RP include

Web applications and Web services can both be Relying Partys.

A relying party (RP) application consumes the tokens issued by a Security Token Service (STS) and extracts the claims from tokens to use them for identity related tasks.

The Challenge#

Online service providers, or Relying Party, are faced with a difficult business challenge. They want to enable their customers to access services and complete transactions with the least amount of friction possible, while minimizing fraud risk and meeting regulatory compliance requirements in their market or geography.

Relying Party may implement a Digital Identity Acceptance Policy!! Relying Party and Public Key Infrastructure The Clients in Public Key Infrastructure are the Relying Party and are relying on (ie Trusting) the Certificate Authority

More Information#

There might be more information for this subject on one of the following:
Please see our Copyright And Intellectual Property Page and Standard Disclaimer Pages!