-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDAP needs refactoring #82
Labels
Comments
etj
added a commit
that referenced
this issue
Jan 24, 2017
Externalize DB/LDAP selection. Add caching to LDAP queries. Downgrade log4j version to 1.x (align to GeoServer) Upgrade spring-ldap version to 2.x (align to Spring 4 core) Upgrade geoserver-manager to 1.6. Clean up obsolete pre-3.0 methods (user and groups refs by id) Clean up configuration files (#16) Remove some dead code in GWT client. Improve users and groups loading in GWT client. Clean up misplaced log4j.properties files. Authorization request filters now can only specify either the user or the group.
nmco
pushed a commit
to nmco/geofence
that referenced
this issue
Apr 20, 2018
Externalize DB/LDAP selection. Add caching to LDAP queries. Downgrade log4j version to 1.x (align to GeoServer) Upgrade spring-ldap version to 2.x (align to Spring 4 core) Upgrade geoserver-manager to 1.6. Clean up obsolete pre-3.0 methods (user and groups refs by id) Clean up configuration files (geoserver#16) Remove some dead code in GWT client. Improve users and groups loading in GWT client. Clean up misplaced log4j.properties files. Authorization request filters now can only specify either the user or the group.
nmco
pushed a commit
to nmco/geofence
that referenced
this issue
Apr 20, 2018
Externalize DB/LDAP selection. Add caching to LDAP queries. Downgrade log4j version to 1.x (align to GeoServer) Upgrade spring-ldap version to 2.x (align to Spring 4 core) Upgrade geoserver-manager to 1.6. Clean up obsolete pre-3.0 methods (user and groups refs by id) Clean up configuration files (geoserver#16) Remove some dead code in GWT client. Improve users and groups loading in GWT client. Clean up misplaced log4j.properties files. Authorization request filters now can only specify either the user or the group.
nmco
pushed a commit
to nmco/geofence
that referenced
this issue
Apr 20, 2018
Externalize DB/LDAP selection. Add caching to LDAP queries. Downgrade log4j version to 1.x (align to GeoServer) Upgrade spring-ldap version to 2.x (align to Spring 4 core) Upgrade geoserver-manager to 1.6. Clean up obsolete pre-3.0 methods (user and groups refs by id) Clean up configuration files (geoserver#16) Remove some dead code in GWT client. Improve users and groups loading in GWT client. Clean up misplaced log4j.properties files. Authorization request filters now can only specify either the user or the group.
hwbllmnn
pushed a commit
to hwbllmnn/geofence
that referenced
this issue
Apr 27, 2018
Externalize DB/LDAP selection. Add caching to LDAP queries. Downgrade log4j version to 1.x (align to GeoServer) Upgrade spring-ldap version to 2.x (align to Spring 4 core) Upgrade geoserver-manager to 1.6. Clean up obsolete pre-3.0 methods (user and groups refs by id) Clean up configuration files (geoserver#16) Remove some dead code in GWT client. Improve users and groups loading in GWT client. Clean up misplaced log4j.properties files. Authorization request filters now can only specify either the user or the group.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LDAP module was created before the 3.0 changes (i.e. embeddability in GeoServer) and some methods still reflect the old API behavour.
Since users and roles are no longer needed as FK in Rules, they do not need to be mirrored from the LDAP directory into the GeoFence DB.
Also, users and roles should be referred by name, not by their id (ids in an externalized source do not make much sense).
The text was updated successfully, but these errors were encountered: