🚀 Feature: Implicit Authorization #6

New Issue

OVERLORD · 2025-10-09T16:21:37+03:00

OVERLORD commented

2025-10-09 16:21:37 +03:00

Originally created by @UbiquitousBear on GitHub.

Feature description

Allow OIDC clients to support implicit authorisation flows, which bypass the need for the authenticated user to explicitly approve information required by an OIDC client.

Pitch

In my use-case, very few applications require a user to explicitly approve what information is provided (name, email, groups etc); this is due to the applications being internally built or internally facing and 'trusted'.

Originally created by @UbiquitousBear on GitHub. ### Feature description Allow OIDC clients to support implicit authorisation flows, which bypass the need for the authenticated user to explicitly approve information required by an OIDC client. ### Pitch In my use-case, very few applications require a user to explicitly approve what information is provided (name, email, groups etc); this is due to the applications being internally built or internally facing and 'trusted'.

OVERLORD closed this issue

2025-10-09 16:21:38 +03:00

OVERLORD commented

2025-10-09 16:21:40 +03:00

@stonith404 commented on GitHub:

Thanks for your request. The implicit authorization flow is no longer recommended because it is not considered secure. Because of that we don't plan to implement this flow but encourage the clients to migrate to the authorization code flow.

@stonith404 commented on GitHub: Thanks for your request. The implicit authorization flow is no [longer recommended](https://oauth.net/2/grant-types/implicit/) because it is not considered secure. Because of that we don't plan to implement this flow but encourage the clients to migrate to the authorization code flow.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/pocket-id-pocket-id-2#6