Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to use static token for Connection #186

Open
TakumiHaruta opened this issue Feb 27, 2023 · 3 comments
Open

Add option to use static token for Connection #186

TakumiHaruta opened this issue Feb 27, 2023 · 3 comments

Comments

@TakumiHaruta
Copy link

Description

Want to have the option to use a static token when it creating a connection.
The example is below;

Context

Currently there seems to be only JWTProfile to authorize access from a system client to Zitadel APIs, but we have another use case in the backend, which is to reuse an access token in Authorization header from the frontend request to the Zitadel APIs.

@fforootd
Copy link
Member

fforootd commented Mar 6, 2023

Do I understand you correct that you want to access ZITADELs API's with a PAT (Personal Access Static) which can be statically sent along as authorization header?

PAT guide

Our do you mean something different?

@TakumiHaruta
Copy link
Author

TakumiHaruta commented Mar 7, 2023

@fforootd
Is PAT a static token right?
The PR I opened is for a dynamic access token generated with OIDC in the frontend.

We don't want to let frontend engineers directly use Zitadel APIs, and wrap them in our own backend, so this feature is necessary to directly pass access token from the header in the client request to Zitadel APIs in the backend.

But I think the request format is almost the same as PAT one because it just uses Authorization header

@fforootd
Copy link
Member

fforootd commented Mar 7, 2023

Ah I see. What you need is to run an api that get called with a token from a user and you want to use that token on ZITADEL's api.

@livio-a can you get the PR into a review schedule?

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 a pull request may close this issue.

2 participants