Skip to content

Comments

feat: implement device authentication (no browser)#105

Open
gianarb wants to merge 1 commit intomainfrom
feat/device-auth
Open

feat: implement device authentication (no browser)#105
gianarb wants to merge 1 commit intomainfrom
feat/device-auth

Conversation

@gianarb
Copy link
Collaborator

@gianarb gianarb commented Feb 17, 2026

We need a way to authentication the datumctl even when a browser is not
available. For example inside a container or in a server.

OAuth cover this scenario with device authentication.

Zitadel supports device auth and it is documented here:

https://zitadel.com/docs/guides/integrate/login/oidc/device-authorization

This commit implements this flow when --no-browser is passed to
datumctl auth login

Fixed #104

We need a way to authentication the datumctl even when a browser is not
available. For example inside a container or in a server.

OAuth cover this scenario with device authentication.

Zitadel supports device auth and it is documented here:

https://zitadel.com/docs/guides/integrate/login/oidc/device-authorization

This commit implements this flow when `--no-browser` is passed to
`datumctl auth login`
@gianarb gianarb requested a review from scotwells February 17, 2026 15:22
@gianarb
Copy link
Collaborator Author

gianarb commented Feb 17, 2026

TODO: I think I need to revert the staging client id for zitadel when the official one will be correctly configured

@scotwells
Copy link
Contributor

@gianarb does the new client ID support both device code and PKCE authentication? We may need to select which client to use based on the --no-browser flag.

@gianarb
Copy link
Collaborator Author

gianarb commented Feb 18, 2026 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Authenticate without a browser

2 participants