What is the planned strategy for quarkus-renarde-oidc? continue to extend it with more providers (in that case I could start to have a look and do my change their).
I would also understand if you prefer focusing on major providers in the renarde framework…
From what I saw/understood the classes prepared in quarkus-renarde-oidc are not really meant to be extensible (for the use case of adding a new provider) directly in a quarkus app.
I would be interested by having the possibility to use GitLab as OIDC provider: https://docs.gitlab.com/ee/integration/openid_connect_provider.html
What is the planned strategy for
quarkus-renarde-oidc? continue to extend it with more providers (in that case I could start to have a look and do my change their).I would also understand if you prefer focusing on major providers in the renarde framework…
From what I saw/understood the classes prepared in
quarkus-renarde-oidcare not really meant to be extensible (for the use case of adding a new provider) directly in a quarkus app.What is your advice?