Skip to content
Skip to this exploration
All explorations

Practical self-hosting · beginner

11 · One login, several trust decisions

Understand what an identity provider does and does not authorize.

10 min 5 sectionsv1

What you can take away

  • Trace an OIDC login and separate identity from application permissions.
  • Draw the login path for a fictional application at `lesson.example.com`

Your trail through this idea

Checking saved progress…

A successful single sign-on can still lead to the wrong access level. Ian’s Authentik questions are a useful route into a fundamental distinction: identifying a person and authorizing an action are separate decisions.

Prerequisite: complete the preceding lesson or bring its worksheet.

Mark sections complete when you choose. Reading alone does not mark them.

Understand the system

An identity provider supplies identity information through a supported protocol. The application still needs to decide what that identity can do. Authentik’s OAuth2 provider documentation covers its OAuth2/OIDC configuration. Redirect URIs, issuer configuration, client credentials, and claims have specific roles; substituting similar-looking values is not a sound debugging method.

Think of a login as a bounded exchange among browser, application, and identity provider. A callback should return to an expected application endpoint. The application must validate the received identity evidence and apply its own access rules. A user group claim is only useful if the application interprets it as intended.

Checking saved progress…

Work through the case

Original case: a family reader and an administrator both sign in successfully. The reader should view approved content but cannot edit roles. Testing only the administrator proves very little about least-privilege access. Likewise, logging out of one application does not justify assuming that all related sessions ended.

Checking saved progress…

Make something useful

Try this

Original exercise

Draw the login path for a fictional application at lesson.example.com. Record issuer, allowed callback, requested identity fields, and the reader/admin permission difference as placeholders. Create a test plan with allowed and denied actions for each role. Perform real configuration only in a separate test application after backing up its settings and retaining an independent recovery path.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

Does successful sign-on prove correct application authorization?

Choose one answer

A self-study prompt. You can retry; this is not an exam.

Checking saved progress…

Keep the result and follow the sources

Success is a trust diagram and a negative test, not merely a green login button. The next lesson asks what happens when the identity system itself is the unavailable dependency.

Sources and scope

  • Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
  • Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
  • Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.
Checking saved progress…

These checks are for reflection and practice. Your answers and reflection notes are not sent anywhere.

Back to all explorations