FHow did you configure zitadel and rocketchat?
FHm can you check on the ELB logs what gets sent to the /authorize endpoint?
Fnothing that looks wrong instantly 
Fwhile we support http1.1 and http2 this sounds like a protocol switching issue.
can you set explicit h2 on the upstream?
can you set explicit h2 on the upstream?
Fonly our grpc api requires http2 all other things should work with h1.1 so you can give that a spin
Fwhat happens if you change "parameter name for token = access_token"?
Fno that field is called prefered_username
FYou can find the defaults here https://zitadel.com/docs/apis/openidoauth/claims#standard-claims
ZITADEL asserts claims on different places according to the corresponding specifications or project and clients settings.
FI think you problem is that you also need to add more scopes.
Try
Try
openid profile emailFHaha I take at least the login worked
FI see, you can use an action to produce a similari format.
Maybe this gives you inspiration https://github.com/zitadel/actions/blob/main/examples/custom_roles.js
Maybe this gives you inspiration https://github.com/zitadel/actions/blob/main/examples/custom_roles.js
GitHub
ZITADEL Actions - Easy extensibility with custom code. Think GitHub Actions in an Identity System. - zitadel/actions
FSure, I would love to review a PR for that :gigilove:
We could put it here besides gitlab and others https://github.com/zitadel/zitadel/tree/main/docs/docs/guides/integrate/services
We could put it here besides gitlab and others https://github.com/zitadel/zitadel/tree/main/docs/docs/guides/integrate/services
GitHub
ZITADEL - Identity infrastructure, simplified for you. - zitadel/zitadel