> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/g2p-bridge/deployment/keycloak-client.md).

# Keycloak Client

Historical — the Keycloak/Keymanager crypto backend removed after 1.0.0

{% hint style="warning" %}
**Historical page.** Version 1.0.0 shipped an optional **Keymanager** crypto backend: when enabled, the Bridge authenticated to MOSIP Keymanager as a confidential `g2p-bridge` OIDC client — provisioned by the `keycloak-init` subchart — to validate partner signatures. That backend, the `keycloak-init` dependency, and their `global.g2pBridge*` / `keycloak-init.*` values have been **removed** in later versions and no longer exist in the chart.

The current Bridge verifies partner signatures **in-process** against public keys served by the **Partner Manager (PM)** service (`GET /keys`, unauthenticated) — no Keycloak or key service at runtime. For the current model see [Onboarding Partners](/products/g2p-bridge/deployment/onboarding-partners.md) and [Partner Signing Key](/products/g2p-bridge/deployment/partner-signing-key.md).
{% endhint %}

{% hint style="info" %}
The trial's partner-onboarding Job (`pm-register` / `pm-seed`) still uses a Keycloak client with the `partner_manager` role to *onboard* partners into PM — but that is Partner Manager's `commons-services-staff-portal` client, unrelated to the removed `g2p-bridge` client described above.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/products/g2p-bridge/deployment/keycloak-client.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.