Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Yes, there are ways you can work around it. It  depends on your exact setup what can work there.
What I saw several times before it to use Ory Hydra as your own OAuth2.0 /OIDC provider.

You can dig around on github discussions and in the slack a bit and see if you find something.
If you come up short let me know and I will join the hunt, as the question comes up every once in a while.

But tl;dr: you can workaround but it is not trivial

easiest will probably be to open a browser for that and do the OIDC login there

<@U010UKXCPP0> That is the first approach we considered but we really need login through Facebook. I think it's planned to be not supported after October 5th.

facebook is special anyways 'cause they force you to ship your app with their spyware called "SDK", which we cannot ship as part of our open source software
so facebook support will probably take even longer until we figure that one out

Looking at the issues it seems the flow being considered for oidc support in `/api` is to use the id_token and swap that for a Kratos session token. That would generally work for most providers right?