Skip to content

Fix three broken external links in connect-with-mattr tutorial #6026

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mathushihanratnatheepan wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix three broken external links in connect-with-mattr tutorial #6026

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
371a3a4
Fix three broken external links in connect-with-mattr tutorial
mathushihanratnatheepan Mar 27, 2026
c90721b
Update claimMappings documentation link
mathushihanratnatheepan Mar 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions en/identity-server/7.2.0/docs/references/tutorials/connect-with-mattr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ Follow the steps given below.
- `<TOKEN_ENDPOINT_URL>`: Provide the {{ product_name }} token endpoint URL.
- `<OIDC_APP_CLIENT_ID>`: Provide the OIDC application ID.
- `<OIDC_APP_CLIENT_SECRET>`: Provide the OIDC application secret that you created when configuring the application in {{ product_name }}.
- `claimMappings`: Configure the claims that you need to offer with the verifiable credential to the wallet holder by adding them in the `claimMappings` parameter in the request payload. See the [MATTR-supported credential claim mappings](https://learn.mattr.global/tutorials/web-credentials/issue/oidc-bridge/common-mappings){:target="_blank"}.
- `claimMappings`: Configure the claims that you need to offer with the verifiable credential to the wallet holder by adding them in the `claimMappings` parameter in the request payload. See the [credential configurations](https://learn.mattr.global/docs/credentials/credential-configuration) guide on the MATTR website for claim mapping reference.

!!! note
In the step that displays the QR code, we'll refer to the `id` parameter in the response as `{issuer-id}`.
Expand Down Expand Up @@ -179,7 +179,7 @@ Follow the steps given below.
1. Download the MATTR mobile wallet app to your mobile phone.

!!! note
See [this documentation](https://learn.mattr.global/tutorials/wallets/mattr-wallet) for details.
See [this documentation](https://learn.mattr.global/docs/holding/go-hold/getting-started) for details.

2. Go to the MATTR mobile wallet app and scan the QR code.
3. Click **Proceed** and log in to your account in {{ product_name }}.
Expand Down Expand Up @@ -241,7 +241,7 @@ Let's use a sample MATTR application to perform the credential verification. For
2. Download and configure the MATTR sample application by visiting the GitHub repository below.

```bash
https://github.com/mattrglobal/sample-apps/tree/master/verify-callback-express
https://github.com/mattrglobal/sample-apps
```

Update the environment variables in the `.env` file according to your setup. Specifically, for the `TEMPLATEID` variable, use the ID value you received from the response to the previous request.
Expand Down Expand Up @@ -272,4 +272,4 @@ Let's use a sample MATTR application to perform the credential verification. For
}
```

Now you know how to issue verifiable credentials for wallet holders and how to verify them with MATTR using {{ product_name }}. You can continue to harness the full capabilities that {{ product_name }} provides by customizing the sign-in flow, enhancing application security, etc.
Now you know how to issue verifiable credentials for wallet holders and how to verify them with MATTR using {{ product_name }}. You can continue to harness the full capabilities that {{ product_name }} provides by customizing the sign-in flow, enhancing application security, etc.