mirror of
https://github.com/zitadel/zitadel.git
synced 2024-12-13 19:44:21 +00:00
c347e75485
# Which Problems Are Solved Calls with tokens issued through JWT Profile or Client Credentials Grants were no longer possible and threw a "could not read projectid by clientid (AUTH-GHpw2)" error. ZITADEL checks the allowed origins of an application and load its projectID into the context on any API call. Tokens from service accounts did not contain any clientID and therefore never did that check. But due to a change in https://github.com/zitadel/zitadel/pull/8580, were the service user id was set as client_id in the OIDC session to fix the introspection response (https://github.com/zitadel/zitadel/issues/8590). # How the Problems Are Solved - Check if the project and origin were retrieved and only then check the origins # Additional Changes None. # Additional Context - closes https://github.com/zitadel/zitadel/issues/8676 - relates to https://github.com/zitadel/zitadel/pull/8580 (released on 2.62.0) - relates to https://github.com/zitadel/zitadel/issues/8590 |
||
|---|---|---|
| .. | ||
| integration_test | ||
| access_token.go | ||
| amr_test.go | ||
| amr.go | ||
| auth_request_converter_test.go | ||
| auth_request_converter_v2.go | ||
| auth_request_converter.go | ||
| auth_request.go | ||
| client_converter.go | ||
| client_credentials.go | ||
| client.go | ||
| device_auth.go | ||
| error_test.go | ||
| error.go | ||
| introspect.go | ||
| jwt-profile.go | ||
| key_test.go | ||
| key.go | ||
| op.go | ||
| server_test.go | ||
| server.go | ||
| token_client_credentials.go | ||
| token_code.go | ||
| token_device.go | ||
| token_exchange_converter.go | ||
| token_exchange.go | ||
| token_jwt_profile.go | ||
| token_refresh.go | ||
| token.go | ||
| userinfo_test.go | ||
| userinfo.go | ||