-
Hi, I tried to use a private Gitlab server as an authentication provider. I have no experience with setting up OpenID authentication so I just thought I give it a try. I used the following resources as references:
Unfortunately, the gitlab documentation is not the greatest for this (imo), since the information is a bit spread out... I used Using wave 0.25.2, I get the following error message:
I then tried to do the same request manually with Insomnia to investigate, and it returns an HTML instead of json, so I guess I've been using the wrong API endpoint there. So this leads me to two questions:
Also, I'm happy to be redirect to a Gitlab forum or so, if that's the more appropriate area to ask these questions, but I thought I'd start here 😅 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
Hi @aranvir. It's most likely the wrong provider URL as you say. Its goal is to read As for #1754 this is about using multiple providers at the same time. If you just need to replace Keycloak with Gitlab, that should work fine. Please let me know whether you managed to successfully integrate, would be good to know if there are any other caveats that need to be done on our side to provide a smoother experience. Edit: Maybe this is what you are after? |
Beta Was this translation helpful? Give feedback.
Agreed, we might add an FAQ since the steps should be the same for all the OIDC-compliant providers. Feel free to open a PR with the FAQ list in https://wave.h2o.ai/docs/security/#single-sign-on since you went through all this and know the best what is confusing and what made it click for you.
Edit: Once resolved, mark this as answered so that other people can have easier time finding this.