![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
2.3-beta1 |
|
Assignee:
|
Christian Mueller
|
|
Components:
|
Security |
|
Created:
|
12/Jan/13 9:17 AM
|
|
Description:
|
Since GeoServerUser objects may have additional properties (e. g. employee number) it should be possible to query for users based on properties.
SortedSet<GeoServerUser> getUsersHavingProperty(String propname) throws IOException;
SortedSet<GeoServerUser> getUsersNotHavingProperty(String propname) throws IOException;
SortedSet<GeoServerUser> getUsersHavingPropertyValue(String propname,String propvalue) throws IOException;
Implementations of the GeoServerUserGroupService should have to chance to implement this calls efficiently. At the moment, it is necessary to iterate over all users and check each user object..
An actual example is the auth-key module. It would be nice to have the option to store the unique auth-key (global identifier) as a user property (auth-key=f9ew09sls).
|
|
Project:
|
GeoServer
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Christian Mueller
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
