Organization level identity brokering configuration does not appear to work, or isn't clear
Original message was deleted
FTo trigger the org level brokering there are two options.
1) as soon as the user providers his username zitadel will check the corresponding org settings and render the login page accordingly
2) you can pass along the orgid/name in the authorization call to directly invoke the org login page. Check the scopes here https://zitadel.com/docs/apis/openidoauth/scopes#reserved-scopes
1) as soon as the user providers his username zitadel will check the corresponding org settings and render the login page accordingly
2) you can pass along the orgid/name in the authorization call to directly invoke the org login page. Check the scopes here https://zitadel.com/docs/apis/openidoauth/scopes#reserved-scopes
ZITADEL supports the usage of scopes as way of requesting information from the IAM and also instruct ZITADEL to do certain operations.
FIt should also work if you provide the login_hint https://zitadel.com/docs/apis/openidoauth/endpoints#additional-parameters
OpenID Connect 1.0 Discovery
FBTW we are working on an improved docs for this 
FIdpid is used to directly trigger a certain idp during the flow
FCan you share your auth request (DM if needed) the orgid should work
F
FGreat
FYeah that sounds like a config issue
Fhttps://zitadel.com/docs/guides/integrate/identity-brokering this article should contain the callback path on our end
What is Identity Brokering and Federated Identities?
F(I know we should display it in console) and the idp part will be improved a lot soon
FHaha, not yet (but there is work underway for idp templates) basically we create the most common idps as ready made templates with styling)
FGitHub
Implement idp template possibility, get some inspiration from https://github.com/markbates/goth Acceptance Criteria Implement IDPs below Implement Package with all the providers Define what kind of...
FThat’s the tracking issue
FHappy to assist