|
Issue Type:
|
 Improvement
|
|
Affects Versions:
|
2.3-beta1
|
|
Assignee:
|
Christian Mueller
|
|
Components:
|
Security
|
|
Created:
|
28/Jan/13 7:52 AM
|
|
Description:
|
There are 2 situations where security migration can be avoided.
-
A fresh geoserver 2.3.x install. The directory date/release/security has to be prepared. The admin password is geoserver, the master password is geoserver too.
-
System test setup. The security.zip file is modified and includes the result of
migration from 2.1->2.2 and 2.2–>2.3
The java keystore file cannot be prepared in advance. Sad but true, it is not possible to open a keystore created with Oracle jdk with an IBM jdk. Keystore creation happens on the fly.
|
|
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)
