Closed matbgn closed 1 year ago
I will put this idea on the RoadMap project, I think it would be a good idea.
Based on the actual roadmap what will be a reasonable delay? With absolute no guarantee of course.
There is no other high priority task, so I think I will put it as a next step. So in a week or two based on my free time
FYI I think I will use this package https://github.com/jumbojett/OpenID-Connect-PHP I have pinned it a few days ago, so I will try it ASAP.
😲 If you maintain this timeline I will, for sure, buy you a big coffee!
What do you think, just for fun 😄
🤣 ChatGPT apologies are enormous!
But personally I will go trough passport. It's a good battlefield tested library and I'm sure that you will be able to connect it with Connect2Id in one or the other way.
Lol yes there I can't even ask again 🤣
Yep, passport for me too is the best choice.
@matbgn any suggestions for local OIDC connect provider to make tests?
An easy and straightforward solution would be to use Authentik (https://github.com/goauthentik/authentik), personally I use Keycloak.
@matbgn
I just pushed the OIDC Connect function to dev
branch, before merging it to master, I would like if possible that you test it in your local to check if the logic is good and match your needs.
To make it working in your local environment:
git clone https://github.com/devaslanphp/project-management-docs.git
dev
: git checkout dev
composer install && npm install
.env
file based on docs: https://devaslanphp.github.io/project-management/#/installation?id=configurationOIDC_CLIENT_ID=
OIDC_CLIENT_SECRET=
OIDC_DISCOVERY_ENDPOINT=
OIDC_REDIRECT_URI="${APP_URL}/oidc/callback"
OIDC_REALM="myrealm"
OIDC_URL_AUTHORIZE="${OIDC_DISCOVERY_ENDPOINT}/realms/${OIDC_REALM}/protocol/openid-connect/auth"
OIDC_URL_ACCESS_TOKEN="${OIDC_DISCOVERY_ENDPOINT}/realms/${OIDC_REALM}/protocol/openid-connect/token"
OIDC_URL_RESOURCE_OWNER_DETAILS="${OIDC_DISCOVERY_ENDPOINT}/realms/${OIDC_REALM}/protocol/openid-connect/userinfo"
OIDC_SCOPE="openid"
Make sure you have already configured the OIDC environment variables before trying to authenticate your user based on your OIDC provider, and enabled the OIDC Connect login in your Administration General Settings
FYI To enable / disable login sections (form, oidc and social) you can use the General settings.
@matbgn any news about this?
Finally I managed to deploy it on Caprover and made a PR on the community for its basic installation as a reward (sorry for the delay) see https://github.com/caprover/one-click-apps/pull/888
Next I'll try with OIDC and get back to you or make a new issue specifically for that if needed, but I don't mind so.
As promised the coffee is on its way, enjoy! :coffee:
Finally I managed to deploy it on Caprover and made a PR on the community for its basic installation as a reward (sorry for the delay) see caprover/one-click-apps#888
Next I'll try with OIDC and get back to you or make a new issue specifically for that if needed, but I don't mind so.
That's great, thanks for your help!
As promised the coffee is on its way, enjoy! ☕
Thanks a lot mate! don't hesitate if you need any help, I have a lot to do, but I can help on my free time
Would it be possible to implement a more open protocol for single sign-on like OIDC?
The open-source library Passport.js could be a solution if needed.