Within a federated identity system, which entity accepts tokens from the identity provider?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The relying party is attached to the application or service that a user is trying to access, and it accepts authentication tokens from the user's own identity provider in order to facilitate authentication and access.
The other terms provided are all associated with federated systems, but none is the correct choice in this case.
Within a federated identity system, the entity that accepts tokens from the identity provider is the relying party.
A federated identity system enables users to use a single set of credentials (such as a username and password) to access multiple systems and applications that are part of the federation. This is achieved by using an identity provider (IdP) that authenticates the user and issues a token containing information about the user's identity and authentication status. This token is then presented to the relying party (RP), which uses it to grant access to the requested resource.
The RP is the entity that receives the token from the IdP and uses it to make authorization decisions. The RP can be a web application, a service, or any other system that requires authentication and authorization. The RP must be configured to trust the IdP and to accept the tokens that it issues.
The other options provided in the answers are also important entities within a federated identity system, but they are not the ones that accept tokens from the IdP. The assertion manager is responsible for creating and managing the security tokens that are exchanged between the IdP and the RP. The proxy party acts as an intermediary between the IdP and the RP, providing additional security and functionality. The servicing party is the entity that provides the resource or service that the user is trying to access.