IBMid signs users in with the IBM account used across IBM Cloud and IBM's product estate. It fits enterprise tooling sold into IBM-centric organizations.

## Copy the redirect URI

In the [Authdog console](https://console.authdog.com), select the project and environment, open **Authentication > Providers**, find **IBMid**, and click **Enable**. Copy the redirect URI shown in the form:

```url
https://identity.authdog.com/api/v1/callback/<connectionId>
```

## Create the application

1. Request an OIDC client registration for IBMid through your IBM partner or account contact.
2. Provide the redirect URI from Authdog for allow-listing on the registration.
3. Copy the issued **Client ID** and **Client Secret**.

## Configure Authdog

| Field | Value |
| --- | --- |
| **Client ID** | The client identifier from the provider |
| **Client Secret** | The client secret from the provider |

Save, then toggle the connection **active**.

## What IBMid returns

Authdog requests the `openid profile email` scopes and reads the profile from `https://login.ibm.com/oidc/endpoint/default/userinfo`.

The userinfo endpoint returns the standard OpenID Connect claims — `sub`, email, given and family name.

IBMid registration is not self-service, so allow lead time before a launch that depends on it.

## Test it

1. Open your environment's hosted sign-in page, or link to `https://identity.authdog.com/api/v1/signin/<connectionId>`.
2. Select the IBMid button and complete the flow.
3. Confirm the user appears under **Users** in the console with a IBMid identity linked.

## Troubleshooting

| Symptom | Cause |
| --- | --- |
| `invalid_redirect_uri` | The URI is not on the client registration |
| Redirect or callback URL error | The URI registered with the provider does not match Authdog's exactly |
| Works in one environment only | Each environment has its own `connectionId`, and so its own redirect URI to register |

## Related

| Read | To learn how to |
| --- | --- |
| [Connectors](/docs/connectors) | Set up any other social provider |