|
|
|
Issue Type:
|
 Improvement
|
|
Affects Versions:
|
2.3-beta1
|
|
Assignee:
|
Christian Mueller
|
|
Components:
|
Security
|
|
Created:
|
14/Jan/13 2:22 AM
|
|
Description:
|
The auth key module maps UUIDs (universally unique identifier) to user names. The mapping is stored in securty/auhtkeys.properties. The client authenticates by sending its UUID as an HTTP parameter.
Changes and enhancements
-
Since multiple user/group Services are possible, the authkeys.properties has to be stored in the directory of the service, e. g. security/usergroup/default/authkeys.properties
-
The filter is rewritten for the new security architecture
-
Until now, there was one key mapper implementation using the authkey.properties file. A new key mapper implementation uses user properties. The property is called UUID and is stored with the user object. An efficient implementation is related to https://jira.codehaus.org/browse/GEOS-5557
-
An admin GUI allows configuring such filters.
-
Each key mapper has to implement a method called “synchronize”. This method assures that each user has an UUID. This method can be triggered by the admin GUI.
|
|
Project:
|
GeoServer
|
|
Priority:
|
 Major
|
|
Reporter:
|
Christian Mueller
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your [JIRA administrators](https://jira.codehaus.org/secure/ContactAdministrators!default.jspa).
For more information on JIRA, see: [http://www.atlassian.com/software/jira](http://www.atlassian.com/software/jira)