Portal Client

The portal-odoo client is the central OAuth client used by the Dealership Portal (portal.uaagi-uno.com). Its configuration follows the same pattern as Dealership Clients, with a few key differences.

---

Create the client

1. Navigate to Clients > Create client.
2. Set Client type to OpenID Connect.
3. Set Client ID to portal-odoo.
4. Set Name to UAAGI Dealership Portal.
5. Click Next, then Save.

---

Settings

Configure the same way as a dealership client, but with portal-specific URLs:

Access settings

Field	Value
Root URL	https://portal.uaagi-uno.com
Home URL	https://portal.uaagi-uno.com
Valid redirect URIs	https://portal.uaagi-uno.com/auth_oauth/signin
	https://portal.uaagi-uno.com/*
	https://portal.uaagi-uno.com/web
Valid post logout redirect URIs	https://portal.uaagi-uno.com/*
Web origins	https://portal.uaagi-uno.com
Admin URL	https://portal.uaagi-uno.com

Capability config

Setting	Value
Client authentication	On
Authorization	Off
Standard flow	Checked
All other flows	Unchecked

Login & Logout settings

Same as dealership clients — see Dealership Clients > Step 4.

Credentials

Same as dealership clients — Client Id and Secret. Copy the secret for Odoo Configuration.

Advanced — PKCE

Set Proof Key for Code Exchange Code Challenge Method to S256.

---

Differences from dealership clients

Setting	Portal client	Dealership client
Client ID	portal-odoo	<code>-dealership
All URLs	https://portal.uaagi-uno.com	https://<subdomain>.uaagi-uno.com
Protocol mappers	Has 5 custom mappers (dedicated scope)	Typically none — relies on portal for assignment

---

Protocol mappers

The portal client's dedicated scope (portal-odoo-dedicated) contains the 5 custom attribute mappers that inject dealership assignment claims into the token. See Protocol Mappers for full details.

This is the key difference — the portal client needs these mappers because it is the entry point where Odoo reads user attributes and provisions dealership access.