🚀 Feature: Allow to set the client_secret per API #238

Closed
opened 2025-10-07 23:58:49 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @wrenix on GitHub.

Feature description

For automation purpose it would be nice, if we could force / generate the client_secret (and client_id) for an application.

Pitch

an optinal parameter on the API request (if not set pocket-id will genate it)

Originally created by @wrenix on GitHub. ### Feature description For automation purpose it would be nice, if we could force / generate the client_secret (and client_id) for an application. ### Pitch an optinal parameter on the API request (if not set pocket-id will genate it)
OVERLORD added the feature label 2025-10-07 23:58:49 +03:00
Author
Owner

@Fred-06 commented on GitHub:

Hi,

For an example, oCIS requires a specific client_id (Android, iOS, Desktop).

https://doc.owncloud.com/server/next/admin_manual/configuration/user/oidc/oidc.html#owncloud-desktop-and-mobile-clients

It would therefore be nice if this parameter could be set manually.

Thank's !

@Fred-06 commented on GitHub: Hi, For an example, oCIS requires a specific client_id (Android, iOS, Desktop). https://doc.owncloud.com/server/next/admin_manual/configuration/user/oidc/oidc.html#owncloud-desktop-and-mobile-clients It would therefore be nice if this parameter could be set manually. Thank's !
Author
Owner

@kmendell commented on GitHub:

Pocket ID doesnt allow setting custom client ID's or secrets, But the api should be able to create OIDC clients already and should return the client id and secret to you?

Are you not seeing that behavior?

@kmendell commented on GitHub: Pocket ID doesnt allow setting custom client ID's or secrets, But the api should be able to create OIDC clients already and should return the client id and secret to you? Are you not seeing that behavior?
Author
Owner

@wrenix commented on GitHub:

I see it, but that make it just more complicated for automation.

@wrenix commented on GitHub: I see it, but that make it just more complicated for automation.
Author
Owner

@stonith404 commented on GitHub:

@wrenix Can you explain your use case for needing a static client secret? How would it make this automation more difficult if the OIDC client creation endpoint provides the client secret?

@stonith404 commented on GitHub: @wrenix Can you explain your use case for needing a static client secret? How would it make this automation more difficult if the OIDC client creation endpoint provides the client secret?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id-pocket-id-1#238