Ideally, I'd like to integrate Joplin-Server with KeyCloak as the IAM and OIDC provider. This ticket is for documentation purposes within my fork as something I'd like to explore or implement down the line.
Doing so would allow an organization to manage access to Joplin-Server from their own (likely LDAP/ActiveDirectory) source-of-truth. This would also open doors toward getting SSO capabilities down the line.
I see a Joplin Discourse note, where the OP had started down the path for his own fork, and in there, OP offered a hint in there to use openid-client as a starting-point.
Looks promising, will need to investigate further when I have time. I haven't yet probed to see if OP has a repo available with a changeset I can look at.
Ideally, I'd like to integrate Joplin-Server with KeyCloak as the IAM and OIDC provider. This ticket is for documentation purposes within my fork as something I'd like to explore or implement down the line.
Doing so would allow an organization to manage access to Joplin-Server from their own (likely LDAP/ActiveDirectory) source-of-truth. This would also open doors toward getting SSO capabilities down the line.
I see a Joplin Discourse note, where the OP had started down the path for his own fork, and in there, OP offered a hint in there to use openid-client as a starting-point.
Looks promising, will need to investigate further when I have time. I haven't yet probed to see if OP has a repo available with a changeset I can look at.