🔑 OIDC via FusionAuth
Discover how to seamlessly connect OIDC FusionAuth with Tchop's user management system, enhancing your backend integration for improved security and efficiency.
Connect OIDC with FusionAuth
This how-to guide explains how to connect OIDC FusionAuth to tchop user management and backend. It covers creation of an OIDC connection, a key master, a tenant, a new application, and the required fields for the tchop side.
The guide also includes an example of a configuration file.
Creating OIDC connection
Create Key Master (optional, skip if you already have one)

Open
Settings/Key MasterClick
Generate RSA key pairset
AlgorithmasRS256set
Issuerastchop.io
Create Tenant (optional, skip if your user dataset already exist)
General Tab

JWT tab

Create new application
(optional) select previous created tenant (
tchop.io)
Auth tab

set
Client AuthenticationasNot required when using PKCEset
PKCEasRequireddisable
Generate refresh tokensset
URL validationasAllow wildcardsset
Authorized redirect URLsPlease add redirect URLs here based on the App package name (info to be provided by tchop)
set
Enabled grantsasAuthorization Codeonly
JWT tab

enable
The settingsset
Access token signing keyastchop.io(select previous created keyset)set
Id token signing keyastchop.io(select previous created keyset)
Required fields for tchop side
Fields | Description | Example Value |
|---|---|---|
jwksUri | value from | http://localhost:9011/.well-known/jwks.json |
issuer | name of tenant which created before or | acme.com |
algorithm | type from Master key section, eg RS258 | RS256 |
audience | same as | acme.com |
tokenEndpoint | value from | http://localhost:9011/oauth2/token |
authorizationEndpoint | value from | http://localhost:9011/oauth2/authorize |
userinfoEndpoint | value from | http://localhost:9011/oauth2/userinfo |
clientId | Id of created application, value from | 19fe3351-1e6e-4eef-914d-c74e8ebcb010 |



