Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/actions/spelling/allow.txt
Original file line number Diff line number Diff line change
Expand Up @@ -218,6 +218,7 @@ Phishing
pid
pipeable
pipefail
PKCE
placeholders
platops
plpgsql
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
title: Authentication and authorization
last_reviewed_on: 2026-06-08
review_in: 12 months
weight: 5
---

# <%= current_page.data.title %>

CFT services should use OpenID Connect with CFT IDAM for user authentication.

Authentication and authorization are separate concerns. OpenID Connect establishes the user identity. Services are responsible for their own authorization decisions.

### OpenID Connect flows

Use the authorization code flow for browser-based user authentication.

Use PKCE where the client stack supports it.

Use client credentials only for service-to-service authentication where no user is involved.

Avoid password and implicit grants for new integrations.

For implementation guidance, see the [OpenID Connect Guide for CFT Developers Using CFT IDAM](https://tools.hmcts.net/confluence/spaces/SISM/pages/1973296310/OpenID+Connect+Guide+for+CFT+Developers+Using+CFT+IDAM).
Loading