You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to link a self-hosted OCT server to my own Forgejo/Gitea instance which can act as a Oauth2/OIDC provider.
From the looks of it, the OCT server currently only supports some hard-coded Oauth2 providers (Google and Github?) but you can't specify a custom Oauth2 provider URL (and Name) via ENVs parameters.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @poVoq@yuvipanda, there's another way to solve this even before the additional configuration options are done: use open-collaboration-server as a library to create your own custom server.
You can create your own implementation and bind it to the dependency injection system as seen in container.ts.
Then you can create your own app like in app.ts and load your own InversifyJS container.
The API is in a very early stage and is likely to be broken. In particular, we might switch the dependency injection library (#21). But creating your own custom server app is definitely a scenario we want to support.
I'll unfortunately still just have to wait at least for this feature to land mostly due to time and capacity constraints. So I'll just watch this with excitement :)
I would like to link a self-hosted OCT server to my own Forgejo/Gitea instance which can act as a Oauth2/OIDC provider.
From the looks of it, the OCT server currently only supports some hard-coded Oauth2 providers (Google and Github?) but you can't specify a custom Oauth2 provider URL (and Name) via ENVs parameters.
Thanks!
The text was updated successfully, but these errors were encountered: