> For the complete documentation index, see [llms.txt](https://docs.esignet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esignet.io/home/esignet-2.0.0/local-deployment/local-setup/mock-client-application.md).

# Mock Relying Party

## Mock Relying Party

### What It Is

The Mock Relying Party is a sample OIDC relying party (RP) portal, a stand-in for a real service provider's application, built with React JS. It's made up of two components:

* [**mock-relying-party-ui**](https://github.com/mosip/esignet-mock-services/tree/master/mock-relying-party-ui): the front end, consisting of a login page and a user profile page.
* [**mock-relying-party-service**](https://github.com/mosip/esignet-mock-services/tree/master/mock-relying-party-service): a backend service that hosts a single endpoint to fetch user info

The portal uses the authorization code flow with private key JWT client authentication to fetch the logged-in user's profile — the same flow a real relying party would use in production, not a simplified stand-in for it.

### Why It's Used

Docker Compose and the Postman collection can each exercise pieces of the OIDC flow, but neither shows what it actually looks like from a relying party's side of the exchange — including the private-key-JWT client authentication step, which is one of the more security-sensitive parts of integrating with eSignet. The Mock Relying Party gives you a real, clickable "Log in with eSignet" experience end to end, so you can see exactly what a relying party sends, receives, and does with each token along the way.

### Repository and Setup

{% hint style="info" icon="github" %}
**Codebase**: [esignet-mock-services](https://github.com/mosip/esignet-mock-services/tree/master)
{% endhint %}

{% hint style="info" icon="github" %}
**Setup guide (README)**: [mock-identity-system README ](https://github.com/mosip/esignet-mock-services/blob/master/README.md)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.esignet.io/home/esignet-2.0.0/local-deployment/local-setup/mock-client-application.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.