TrueNamePath Setup Guide

Academic demonstration of context-aware identity management using OAuth/OIDC patterns. This guide covers account setup and core functionality.

Account Creation

Account creation involves two steps with automatic database trigger setup.

Step 1: Basic Registration

Enter your email and create a secure password. No email verification needed for this academic project.

Step 2: Profile Completion

Complete profile setup. Database triggers automatically create the default context and initial name variants.

Default Context Setup

The default context is automatically created via database triggers and requires three mandatory OIDC properties for compliance.

Add Your Names

Go to the Names tab and add different versions of your name like “John Smith”, “John”, or “J. Smith”.

Assign to OIDC Properties

Link your names to OIDC standard properties: name, given_name, and family_name. These three properties are mandatory for default context completion.

Property	Example Assignment
`name`	John Smith
`given_name`	John
`family_name`	Smith

Custom Contexts Creation

Create additional contexts to demonstrate different identity presentations for various OAuth clients.

Create New Contexts

Visit the Contexts tab and create contexts like “Work Colleagues”, “Gaming Friends”, or “HR Systems”.

Set Visibility

Choose visibility levels: public (visible to all), private (only you can see), or restricted (controlled access).

Flexible Assignment

Unlike the default context, custom contexts have no mandatory OIDC property requirements - assign names based on demonstration needs.

Common Context Examples

Common demonstration scenarios:

• Work Colleagues - Professional name for workplace

• Gaming Friends - Casual nickname for gaming

• HR Systems - Formal legal name for official records

• Social Media - Creative handle for online presence

• Family - Familiar name for personal relationships

App Connection

OAuth clients receive identity claims based on assigned contexts, demonstrating context-aware identity resolution.

Authorize Apps

OAuth authorization creates Bearer token sessions tracked in the Connected Apps panel for demonstration purposes.

Assign Contexts

Context assignment determines which identity data is resolved for each OAuth client via the Bearer token API.

Context Completeness

Green checkmarks indicate contexts have all required OIDC properties assigned for complete claims resolution.

What Apps See:

{
  "name": "John Smith",
  "given_name": "John", 
  "family_name": "Smith",
  "context": "Work Colleagues"
}

OAuth clients receive OIDC-compliant identity claims resolved from the assigned context via the Bearer token API.

Understanding the Rules

Learn the important rules that keep your identity management safe and consistent.

Protected Names

You can't delete names that are currently assigned to contexts. Unassign them first if you need to remove them.

Default Context Requirements

Your default context must have names assigned to name, given_name, and family_name properties to be considered complete.

Assignment Visibility

Look for badges that show where each name is being used, helping you understand the impact of any changes.

Safe Changes

The system will guide you through replacing names safely without breaking your existing app connections.

This demonstration system showcases context-aware identity management as part of a university final project exploring OAuth/OIDC patterns and privacy-by-design principles.