# Registering Client ID for Client App

**URL:** <https://forum.solidproject.org/t/registering-client-id-for-client-app/5646>\
**Category:** General Discussion\
**Created:** [September 20, 2022, 6:32pm UTC](https://forum.solidproject.org/t/registering-client-id-for-client-app/5646 "2022-09-20T18:32:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gaz009](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@gaz009](https://forum.solidproject.org/u/gaz009)\
**Post date:** [September 20, 2022, 6:32pm UTC](https://forum.solidproject.org/t/registering-client-id-for-client-app/5646/1 "2022-09-20T18:32:28Z")

</div>

Hello all,

I finished a client app that interacts with SOLID servers. I was looking through the SOLID-OIDC Primer and noticed their example app had a webID associated with it. How would I go about enabling this for my client application?

---

<div class="post-metadata">

**Author:** ![ThisIsMissEm](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/thisismissem/32/3166_2.png) [@ThisIsMissEm](https://forum.solidproject.org/u/ThisIsMissEm)\
**Post date:** [September 20, 2022, 9:37pm UTC](https://forum.solidproject.org/t/registering-client-id-for-client-app/5646/2 "2022-09-20T21:37:45Z")

</div>

Hi! If you’re referring to the diagram in section 4.1, it’s actually incorrect at step 8. It should read “validates redirect url with ClientID”

Section 4.1.7 is also incorrect, arguably, as it uses “webid” to describe a public client identifier document. I’ve opened a PR to try to fix that.

* * *

All that said though, it is also possible that a client may have it’s own WebID as well as a Client ID Document. Though, there’s currently no bi-directional link between the two. To gain said WebID, you’d just register as any other used on a Solid Server of your choice. The use-case for this is if your application acts as itself server-side (e.g., an indexer service might have a WebID and a Client ID Document; You’d then grant access to resources via ACP that match on the WebID and the Client ID IRI, meaning that both the client and the WebID need to match to allow access to the resource)

For typical Solid OIDC usage, this isn’t that common though.

---

<div class="post-metadata">

**Author:** ![ThisIsMissEm](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/thisismissem/32/3166_2.png) [@ThisIsMissEm](https://forum.solidproject.org/u/ThisIsMissEm)\
**Post date:** [September 20, 2022, 9:38pm UTC](https://forum.solidproject.org/t/registering-client-id-for-client-app/5646/3 "2022-09-20T21:38:49Z")

</div>

The current Editor’s Draft of the Solid OIDC Primer also clarifies this a bit: [Solid-OIDC Primer](https://solid.github.io/solid-oidc/primer/)

---

<div class="post-metadata">

**Author:** ![Lauvdb](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/lauvdb/32/3455_2.png) [@Lauvdb](https://forum.solidproject.org/u/Lauvdb)\
**Post date:** [September 27, 2022, 9:31am UTC](https://forum.solidproject.org/t/registering-client-id-for-client-app/5646/4 "2022-09-27T09:31:04Z")

</div>

Hi gaz009,

You can take a look at this running example here: [My Move: A running example](https://docs.use.id/docs/the-moving-plan-app-a-running-example)

You can also check out use.id for getting a managed WebID for your application.