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- "claims aware application"
- "claims-based application"
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:- AS Exchange
- Acceptable Use
- Accreditation Authority
- Acr
- Acr_values
- Assertion
- Attribute references
- Authentication
- Authentication Context Class
- Authentication Context Class Reference
- Authentication Method
- Authentication Request
- Authenticator Assurance Levels
- Authorization Server Request End-User Consent-Authorization
- Backchannel_logout_session_required
- Backchannel_logout_session_supported
- Backchannel_logout_uri
- Biometric Data Challenges
- Certificate
- Certificate Authority
- Certificate Validation
- Check_session_iframe
- Claim
- Client Authentication Methods
- Closed-Loop Authentication
- Context Based Access Control
- Covert Redirect Vulnerability
- Data Accuracy
- Data Classification
- Data Origin
- Data Pedigree
- Data Privacy
- Data Provenance
- DefinitionTokenService
- Digital Identity
- Digital Identity Acceptance Policy
- End_session_endpoint
- FAL 2
- FAL 3
- FIDO Authenticator
- FIDO Client
- FIDO Relying Party
- FIDO Server
- Federation
- Federation Assurance Level
- Federation Models
- Frontchannel_logout_session_required
- Frontchannel_logout_session_supported
- Frontchannel_logout_uri
- Glossary Of LDAP And Directory Terminology
- Id_token_encrypted_response_alg
- Id_token_signed_response_alg
- Identity Assurance
- Identity Assurance Level
- Identity Ecosystem Framework
- Identity Federation
- Identity Proofing
- Initiate_login_uri
- JWK Set
- Jwks_uri
- Kerberos Principal
- Know Your Customer
- LOA 2
- LOA 3
- Law of Consistent Experience Across Contexts
- Law of Justifiable Parties
- Legitimacy of Social Login
- Locale
- Logging Out
- Login_hint
- Logout Token
- Lua-resty-openidc
- M-04-04 Level of Assurance (LOA)
- Mobile Operator Discovery, Registration & Authentication
- NIST.IR 7817
- NISTIR 8112
- National Strategy for Trusted Identities in Cyberspace
- OAuth
- OAuth 2.0 Actors
- OAuth 2.0 Vulnerabilities
- OAuth Client
- OAuth Dynamic Client Registration Metadata
- OAuth Scope Validation
- OAuth Scopes
- Online Certificate Status Protocol
- Op_policy_uri
- Open Identity Trust Framework
- Open-Loop Authentication
- OpenAM Endpoints
- OpenID
- OpenID Connect
- OpenID Connect Account Porting
- OpenID Connect Authentication Response
- OpenID Connect Back-Channel Logout
- OpenID Connect Backchannel Authentication
- OpenID Connect Client Initiated Backchannel Authentication Flow
- OpenID Connect Discovery
- OpenID Connect Federation
- OpenID Connect Federation Async
- OpenID Connect Front-Channel Logout
- OpenID Connect ImplementerS Guides
- OpenID Connect Profile for SCIM Services
- OpenID Connect Scopes
- OpenID Connect Session Management
- OpenID Connect Standard Claims
- OpenID Connect for Identity Assurance
- OpenID Provider Authentication Policy Extension
- OpenID Provider Issuer Discovery
- OpenID.Registration
- Openid-configuration
- Pairwise Pseudonymous Identifier
- Passwordless SMS Authentication
- Privacy Considerations
- RP
- Relying Party
- Request_object_encryption_alg
- Request_object_signing_alg
- SAML
- SP
- Service Provider
- Single Sign-On Scenarios
- Social Websites
- Sovrin
- The Laws of Relationships
- Token Binding over HTTP
- Trust Anchor
- Trust Model
- U-Prove
- U2F
- UserInfo Request
- UserInfo Response
- Vector of Trust Request
- Vectors of Trust
- Verified_claims
- Web Authentication API
- WebAuthn Relying Party
- Why OpenID Connect
- Yadis
- [#1] - http://www.oasis-open.org/committees/download.php/21111/saml-glossary-2.0-os.html
- Retrieved 2013-04-10