Originally created by @Joly0 on GitHub (Apr 25, 2025).
Hey, would be great if Komodo supported more authentication methods for users (i am thinking similar to portainer with ldap and microsoft (azure) active directory), but there are definitely some other authentication methods that would be nice to have added :)
Originally created by @Joly0 on GitHub (Apr 25, 2025).
Hey, would be great if Komodo supported more authentication methods for users (i am thinking similar to portainer with ldap and microsoft (azure) active directory), but there are definitely some other authentication methods that would be nice to have added :)
@joakimkingstrom commented on GitHub (Aug 7, 2025):
I can confirm that Azure/Entra already works.
First of you all you need to create a new app registration in Entra (not an enterprise application, which is what you'd do for SAML).
Once that's done you need to create a client secret on the "Certificates & Secrets" tab. Bear in mind that it's the 'Value' you need to enter as the client secret, not the "Secret ID".
The client ID is the "Application (client) ID" from the "overview" page of the app registration.
You get the URL for the KOMODO_OIDC_PROVIDER variable by clicking on the Endpoints button on the "Overview" page. You need to copy the URL called "OpenID Connect metadata document" at the bottom of the list of endpoints, and then strip away "/.well-known/openid-configuration" from that URL. You'll end up with a URL just like the one below, but with its own unique UUID.
All in all the variables should look something like this:
And don't worry, the above values are all randomly generated ;)
@joakimkingstrom commented on GitHub (Aug 7, 2025):
I can confirm that Azure/Entra already works.
First of you all you need to create a new app registration in Entra (_not_ an enterprise application, which is what you'd do for SAML).
Once that's done you need to create a client secret on the "Certificates & Secrets" tab. Bear in mind that it's the 'Value' you need to enter as the client secret, not the "Secret ID".
The client ID is the "Application (client) ID" from the "overview" page of the app registration.
You get the URL for the KOMODO_OIDC_PROVIDER variable by clicking on the Endpoints button on the "Overview" page. You need to copy the URL called "OpenID Connect metadata document" at the bottom of the list of endpoints, and then strip away "/.well-known/openid-configuration" from that URL. You'll end up with a URL just like the one below, but with its own unique UUID.
All in all the variables should look something like this:
KOMODO_OIDC_ENABLED=true
KOMODO_OIDC_PROVIDER=https://login.microsoftonline.com/3518312a-5f42-421e-9757-947017bc8043/v2.0
KOMODO_OIDC_CLIENT_ID=e82db551-7233-46c5-9935-f23c20401cdd
KOMODO_OIDC_CLIENT_SECRET=6UTvJyW*qxQs832RGCt--qLbH@aw*oZm
KOMODO_OIDC_USE_FULL_EMAIL=true
And don't worry, the above values are all randomly generated ;)
Yes thanks for that post.
I think i would be helpful is somebody can add the documentation for entra id to this site: https://komo.do/docs/setup/advanced
Thanks and greetings
@virus4sepp commented on GitHub (Aug 28, 2025):
Yes thanks for that post.
I think i would be helpful is somebody can add the documentation for entra id to this site: https://komo.do/docs/setup/advanced
Thanks and greetings
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Joly0 on GitHub (Apr 25, 2025).
Hey, would be great if Komodo supported more authentication methods for users (i am thinking similar to portainer with ldap and microsoft (azure) active directory), but there are definitely some other authentication methods that would be nice to have added :)
@joakimkingstrom commented on GitHub (Aug 7, 2025):
I can confirm that Azure/Entra already works.
First of you all you need to create a new app registration in Entra (not an enterprise application, which is what you'd do for SAML).
Once that's done you need to create a client secret on the "Certificates & Secrets" tab. Bear in mind that it's the 'Value' you need to enter as the client secret, not the "Secret ID".
The client ID is the "Application (client) ID" from the "overview" page of the app registration.
You get the URL for the KOMODO_OIDC_PROVIDER variable by clicking on the Endpoints button on the "Overview" page. You need to copy the URL called "OpenID Connect metadata document" at the bottom of the list of endpoints, and then strip away "/.well-known/openid-configuration" from that URL. You'll end up with a URL just like the one below, but with its own unique UUID.
All in all the variables should look something like this:
KOMODO_OIDC_ENABLED=true
KOMODO_OIDC_PROVIDER=https://login.microsoftonline.com/3518312a-5f42-421e-9757-947017bc8043/v2.0
KOMODO_OIDC_CLIENT_ID=e82db551-7233-46c5-9935-f23c20401cdd
KOMODO_OIDC_CLIENT_SECRET=6UTvJyWqxQs832RGCt--qLbH@awoZm
KOMODO_OIDC_USE_FULL_EMAIL=true
And don't worry, the above values are all randomly generated ;)
@Joly0 commented on GitHub (Aug 8, 2025):
Just tried it and can confirm it works :D
@virus4sepp commented on GitHub (Aug 28, 2025):
Yes thanks for that post.
I think i would be helpful is somebody can add the documentation for entra id to this site: https://komo.do/docs/setup/advanced
Thanks and greetings