Repository navigation
Add support for custom OIDC Provider #12
Description
Activity
It will be eventually. But not yet. It requires changes to both cloud-api and fairly core code in the cloud implantation on the kvm.
Reacted by GunniSurely this is a most wanted feature. We're holding off buying dozens of JetKVM until this has been implemented. I'm sure a lot of other enterprises are waiting for this too.
Reacted by Nico Finkernagel, Stan B, Rene 'Renne' Bartsch, Tom Beech, Jonas Westphal and ItsMaxiKaksiSurely this is a most wanted feature. We're holding off buying dozens of JetKVM until this has been implemented. I'm sure a lot of other enterprises are waiting for this too.
Exactly. We’d be happy to support you with a donation so you can implement this. Unfortunately, there’s no chance for us to switch from our current setup to Google Workspace.
Reacted by SyI also think that this is a big feature which would help alot of customers.
Reacted by SyHas there been any progress on this feature implementation? There has been no word or improvements on the cloud-api since publishing the code.
Reacted by SyAny news?
Reacted by Rafael, Jonas Westphal, Tom Beech and SyReacted by jordykre21 and SyWhat's the progress on this one? I'd like to use this feature.
Reacted by Sy and ItsMaxiKaksiStill nothing?
Greetings, I would like to make my semi-annual notification that I am significantly interested in this feature, and would like to know if there has been any updates on implementation?
NOTE: I performed a full test by of the Cloud UI by self hosting a build within a docker container, and performed the adoption of my JetKVM into my self hosted Cloud UI environment. However, the limitation of the Cloud UI to Google authentication, significantly hinders self hosting of the Cloud UI, especially in a fully air-gapped network environment, as the Google authentication apparatus needs to contact the google cloud infrastructure to authenticate. What is requested, is that the environment variables be made agnostic to any Single Sign-on provider, so that the Cloud UI can be authenticated against a locally hosted SSO provider. I appreciate your work, and hope that this can indeed become a reality.I despise cloud api, and i want oidc, please allow oidc when reverse proxying locally to jetkvm, I'd like to use pocket-id, note that jetkvm/kvm#429 is still broken despite being closed.
is there any progress on getting this pull request merged?
Is it possible to add an option to configure a custom OIDC Provider for example Authentik, Keycloak, etc.?