FHei @karanbir We just released that in the newest release. We deployed it yesterday to our cloud. if you are on self hosting make sure to update to the newest release: https://github.com/zitadel/zitadel/releases/tag/v2.20.0
GitHub
Release notes
This release we want to specially honour our external contributors for their effort, as we had a lot of contributions in the past two weeks.
JWT Access Token for Service Accounts - C...
This release we want to specially honour our external contributors for their effort, as we had a lot of contributions in the past two weeks.
JWT Access Token for Service Accounts - C...
F:gigilove:
Fgreat to hear that
FService accounts are there if you want to access data from zitadels APIs or a third party that trusts zitadel
FThe grant type jwt bearer is only there as alternative to client credentials to authenticate your client against zitadel to access the token or intorospect endpoint
FCan you share what you are trying to do?
FOk you want to authenticate a client
FAnd not get a token for the client
FWhat language are you using?
FOk if you use postman use client credentials
FIt is used for authentication of machines I.e service accounts
FThe grant-type bearer is used to authenticate a client
FThis originated from this spec https://www.rfc-editor.org/rfc/rfc7523
FOn what endpoint do you use this?
FIt will not work on /token
FOnly introspection
FIt sends along the token of the client and the access token of a user
FIt can replace the client credentials grant
FWell it can be used against the token endpoint but it needs to have a code from the authorization code flow
FDocs are definitely worth improving 
FWhen I am back at a pc I can try and create a better explanation for this 
FLet me try again later