You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to enable ldap-auth. Following the documentation I've created a new docker image including the ep_ldapauth_ng plugin. I think the plugin is working because it complained about a self signed certificate (using ldaps://, so I switched to ldap:// for the start).
settings.json contains is a copy of the settings-docker-template with the added ldap-config.
The container starts, the admin-page shows the loaded plugin. But the user does not see any login screen, he/she can start creating pads without entering any credentials.
The plugin seems to be a bit older, latest commit was about 3 years ago. Is anyone using this plugin successfully?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am trying to enable ldap-auth. Following the documentation I've created a new docker image including the ep_ldapauth_ng plugin. I think the plugin is working because it complained about a self signed certificate (using ldaps://, so I switched to ldap:// for the start).
The container will be started using:
settings.json contains is a copy of the settings-docker-template with the added ldap-config.
The container starts, the admin-page shows the loaded plugin. But the user does not see any login screen, he/she can start creating pads without entering any credentials.
The plugin seems to be a bit older, latest commit was about 3 years ago. Is anyone using this plugin successfully?
Mathias
Beta Was this translation helpful? Give feedback.
All reactions