Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian
+0
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Wed, Nov 14, 2012 at 4:42 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Thanks for putting this together Christian, definitely a good improvement since as you point out the security filter stuff is still a bit strange to configure. A couple of questions / comments.
Minor: I made some comments on some trivial patch cleanup, not sure if those got addressed.
And the question is how does this affect the configuration stored on disk under the security/filter directory? Like for constant filter chains do we still have a configuration for it stored on disk? It would be good to get a picture of that.
Also, since this is a change to configuration it should also be documented in the user guide for folks who will eventually upgrade to whatever version this makes it into.
http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
On Fri, Nov 16, 2012 at 3:08 AM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:
+0
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.Ing. Alessio Fabiani
@alfa7691
Founder/Technical LeadGeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Wed, Nov 14, 2012 at 4:42 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Wed, Nov 14, 2012 at 4:42 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
+0, I don’t really understand the proposal (could not find the time to wrap my head
around the new security subsystem still), trusting Justin’s judgement here
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
Justin, your comments are already applied.
There are minor changes in the security/filter directory.
The major changes are in the config file for the security manager itself. The chains are stored in this file.
Thanks for remembering me about the documentation about migration. I will modify the migration slightly to give users the chance to revert back. (renaming modified *.xml files to *.xml.2.2.0) and document this.
Cheers
2012/11/20 Justin Deoliveira <jdeolive@anonymised.com>
Thanks for putting this together Christian, definitely a good improvement since as you point out the security filter stuff is still a bit strange to configure. A couple of questions / comments.
Minor: I made some comments on some trivial patch cleanup, not sure if those got addressed.
And the question is how does this affect the configuration stored on disk under the security/filter directory? Like for constant filter chains do we still have a configuration for it stored on disk? It would be good to get a picture of that.
Also, since this is a change to configuration it should also be documented in the user guide for folks who will eventually upgrade to whatever version this makes it into.
http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
On Fri, Nov 16, 2012 at 3:08 AM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:
+0
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.Ing. Alessio Fabiani
@alfa7691
Founder/Technical LeadGeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Wed, Nov 14, 2012 at 4:42 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hey Christian,
To round this thread out, I am +1 on the proposal. However, I don’t think it should be backported to the stable branch, mostly due to the configuration migration that is needed. I think it is good practice to require a new minor version change for that.
This will also give the change some time to settle on master.
-Justin
On Tue, Nov 20, 2012 at 8:18 AM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Justin, your comments are already applied.
There are minor changes in the security/filter directory.
- adding the new role filter (passing back the roles in an HTTP header attribute)
- The logout filter has an additional field “redirectURL”
The major changes are in the config file for the security manager itself. The chains are stored in this file.
Thanks for remembering me about the documentation about migration. I will modify the migration slightly to give users the chance to revert back. (renaming modified *.xml files to *.xml.2.2.0) and document this.
Cheers
2012/11/20 Justin Deoliveira <jdeolive@anonymised.com>
Thanks for putting this together Christian, definitely a good improvement since as you point out the security filter stuff is still a bit strange to configure. A couple of questions / comments.
Minor: I made some comments on some trivial patch cleanup, not sure if those got addressed.
And the question is how does this affect the configuration stored on disk under the security/filter directory? Like for constant filter chains do we still have a configuration for it stored on disk? It would be good to get a picture of that.
Also, since this is a change to configuration it should also be documented in the user guide for folks who will eventually upgrade to whatever version this makes it into.
http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
On Fri, Nov 16, 2012 at 3:08 AM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:
+0
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.Ing. Alessio Fabiani
@alfa7691
Founder/Technical LeadGeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Wed, Nov 14, 2012 at 4:42 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
+0 for me, do not feel I understand the security changes quite yet
–
Jody Garnett
On Wednesday, 5 December 2012 at 12:54 AM, Justin Deoliveira wrote:
Hey Christian,
To round this thread out, I am +1 on the proposal. However, I don’t think it should be backported to the stable branch, mostly due to the configuration migration that is needed. I think it is good practice to require a new minor version change for that.
This will also give the change some time to settle on master.
-Justin
On Tue, Nov 20, 2012 at 8:18 AM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Justin, your comments are already applied.
There are minor changes in the security/filter directory.
- adding the new role filter (passing back the roles in an HTTP header attribute)
- The logout filter has an additional field “redirectURL”
The major changes are in the config file for the security manager itself. The chains are stored in this file.
Thanks for remembering me about the documentation about migration. I will modify the migration slightly to give users the chance to revert back. (renaming modified *.xml files to *.xml.2.2.0) and document this.
Cheers
2012/11/20 Justin Deoliveira <jdeolive@…1501…>
Thanks for putting this together Christian, definitely a good improvement since as you point out the security filter stuff is still a bit strange to configure. A couple of questions / comments.
Minor: I made some comments on some trivial patch cleanup, not sure if those got addressed.
And the question is how does this affect the configuration stored on disk under the security/filter directory? Like for constant filter chains do we still have a configuration for it stored on disk? It would be good to get a picture of that.
Also, since this is a change to configuration it should also be documented in the user guide for folks who will eventually upgrade to whatever version this makes it into.
http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
On Fri, Nov 16, 2012 at 3:08 AM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:
+0
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.Ing. Alessio Fabiani
@alfa7691
Founder/Technical LeadGeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Wed, Nov 14, 2012 at 4:42 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
+0.5 (enthusiastic support combined with my solid lack of understanding of the security subsystem).
On 14/11/12 23:42, Christian Mueller wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82+-+Reworking+security+filter+chains
Thanks to all
Christian
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Hi all
First, thanks for your votes.
Justin, I feared the discussion about the backport and I also feel uncomfortable about the migration within 2.2.x. But lets have a look at the current situation.
IMHO GSIP-82 is not a pure improvement proposal. In fact, it is a cumulative bugfix (especially for the GUI) and it makes GUI filter chain configuration possible. It also adds validation code to prevent misconfiguration concerning filter chains. Within the last weeks, I had to answer security questions and mostly I had to put people off to future versions. Within the last days look at
or
Another fact is that the filter tutorials have to be reworked, because people have problems with them (me too). I have this on my list after GSIP 82, otherwise it does not make sense.
Additionally, CAS works quite will based on GSIP 82. There are two alternatives:
Doing a backport and harvest the fruits of our common efforts
Avoiding the backport and
At the end of the day, I would like to backport and avoid all this questions and time spent (from the users and mine) to get forward.
Perhaps I can make your decision easier. What about 2 commits on master, the first for GSIP-82 and a second for CAS. Then you can have a look at the commit and decide.
Cheers
Christian
2012/12/5 Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
+0.5 (enthusiastic support combined with my solid lack of understanding of the security subsystem).
On 14/11/12 23:42, Christian Mueller wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
I struggle to understand the implications of the backport, but I wholely
support the development of the security fix. The demand for a solution
is there and semi-functional bits are just time-consuming and
frustrating for users. As a user, what I dont want is an upgrade to
geoserver that breaks functions my application depends on. (eg
wmsgetFeature on SDE during the 2.1.3 to 2.1.4 ). Developer comfort
for APIs seems a little secondary On the whole, this looks likely
to fix more bugs than it creates.
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents.
Hey Christian,
I certainly understand your desire to backport, I think we all have this desire when we do something on master that improves a specific feature or subsystem. But we have to have be disciplined on this regard so we try to provide our selves with rules that determine if something is “backportable”. And one of those rules is not changing the data directory / configuration format between releases of the stable series. Doing so basically would not allow users to freely move between minor versions which is something we have always avoided.
So i guess a question is whether this change forward compatible as well as backward compatible. If it is then I think we can start to have a discussion about backporting, but if it isn’t i think that ends the conversation.
If it is forward compatible it is also common / best practice to allow for a decent time period for a new feature to sit on master before its backported to stable, so it gets some extended exposure by other devs in order to:
-Justin
On Wed, Dec 5, 2012 at 9:20 AM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Hi all
First, thanks for your votes.
Justin, I feared the discussion about the backport and I also feel uncomfortable about the migration within 2.2.x. But lets have a look at the current situation.
IMHO GSIP-82 is not a pure improvement proposal. In fact, it is a cumulative bugfix (especially for the GUI) and it makes GUI filter chain configuration possible. It also adds validation code to prevent misconfiguration concerning filter chains. Within the last weeks, I had to answer security questions and mostly I had to put people off to future versions. Within the last days look at
or
Another fact is that the filter tutorials have to be reworked, because people have problems with them (me too). I have this on my list after GSIP 82, otherwise it does not make sense.
Additionally, CAS works quite will based on GSIP 82. There are two alternatives:
Doing a backport and harvest the fruits of our common efforts
Avoiding the backport and
- telling users to wait on 2.3.x for security configuration concerning authentication mechanisms
- removing CAS from the 2.2.x download page
- hope that only few admins invest their time in such configurations (we offer it officially , but it does not work)
At the end of the day, I would like to backport and avoid all this questions and time spent (from the users and mine) to get forward.
Perhaps I can make your decision easier. What about 2 commits on master, the first for GSIP-82 and a second for CAS. Then you can have a look at the commit and decide.
Cheers
Christian2012/12/5 Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
+0.5 (enthusiastic support combined with my solid lack of understanding of the security subsystem).
On 14/11/12 23:42, Christian Mueller wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hi Justin
The GSIP-82 patch requires a new section in http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
If this is not possible between 2.2.x versions, the backport is not possible. Please tell me.
As a developer I am not keen on the backport. It is much easier for me to put my focus on 2.3.x only. As a user, I would be frustrated. As an example, on some chains you can add/remove filters, press save and everything looks ok. After reopening the panel you will get a surprise. The changes are lost. I know from some users that they are modifying the security config.xml manually to get changes saved. This is one example why I want to do the backport.
Another example: Add remove/filters from a chain and change the selection in the filter chain drop box → changes lost.
I do not insist on the backport , but I want to point out that for 2.2.x it is better to avoid configuring authentication mechanisms, an admin needs some luck to get his needed configuration working. (if it is possible at all).
For future user mails in this area, I will advise users to wait for 2.3.0. It also does not make sense to invest in bugfixes concerning filter chains on 2.2.x without the backport.
Anyways, thanks for the discussion and I will start applying the patch to 2.3.x
Christian
2012/12/5 Justin Deoliveira <jdeolive@anonymised.com>
On Wed, Dec 5, 2012 at 9:20 AM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Hi all
First, thanks for your votes.
Justin, I feared the discussion about the backport and I also feel uncomfortable about the migration within 2.2.x. But lets have a look at the current situation.
IMHO GSIP-82 is not a pure improvement proposal. In fact, it is a cumulative bugfix (especially for the GUI) and it makes GUI filter chain configuration possible. It also adds validation code to prevent misconfiguration concerning filter chains. Within the last weeks, I had to answer security questions and mostly I had to put people off to future versions. Within the last days look at
or
Another fact is that the filter tutorials have to be reworked, because people have problems with them (me too). I have this on my list after GSIP 82, otherwise it does not make sense.
Additionally, CAS works quite will based on GSIP 82. There are two alternatives:
Doing a backport and harvest the fruits of our common efforts
Avoiding the backport and
- telling users to wait on 2.3.x for security configuration concerning authentication mechanisms
- removing CAS from the 2.2.x download page
- hope that only few admins invest their time in such configurations (we offer it officially , but it does not work)
At the end of the day, I would like to backport and avoid all this questions and time spent (from the users and mine) to get forward.
Perhaps I can make your decision easier. What about 2 commits on master, the first for GSIP-82 and a second for CAS. Then you can have a look at the commit and decide.
Cheers
Christian2012/12/5 Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
+0.5 (enthusiastic support combined with my solid lack of understanding of the security subsystem).
On 14/11/12 23:42, Christian Mueller wrote:
Please vote on
http://geoserver.org/display/GEOS/GSIP+82±+Reworking+security+filter+chains
Thanks to all
Christian–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Thu, Dec 6, 2012 at 2:04 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Hi Justin
The GSIP-82 patch requires a new section in http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
If this is not possible between 2.2.x versions, the backport is not possible. Please tell me.
The criteria is simple. Assuming 2.2.3 has the fix, can someone
edit the data directory with it, decide someone is off, and go back to 2.2.2, and have 2.2.2 still
be able to open it without problems?
Btw, backport wise, it’s getting late, the window for backports
is closing today, 15 days from the release as per our recent discussion on backports, though 1-2 days
off it won’t be the end of the world (at least for me).
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
Hi Andrea
2012/12/6 Andrea Aime <andrea.aime@anonymised.com>
On Thu, Dec 6, 2012 at 2:04 PM, Christian Mueller <mcrmcr21@anonymised.com> wrote:
Hi Justin
The GSIP-82 patch requires a new section in http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
If this is not possible between 2.2.x versions, the backport is not possible. Please tell me.The criteria is simple. Assuming 2.2.3 has the fix, can someone
edit the data directory with it, decide someone is off, and go back to 2.2.2, and have 2.2.2 still
be able to open it without problems?
No. I think this the sudden death of the backport discussion :-).
I will focus on 2.3.x and stop bug fixing concerning filter chains in 2.2.x.
CAS will also work starting with 2.3.x. Can somebody stop the publishing of the CAS 2.2.x extension to the download page.
Cheers
Christian
Btw, backport wise, it’s getting late, the window for backports
is closing today, 15 days from the release as per our recent discussion on backports, though 1-2 days
off it won’t be the end of the world (at least for me).Cheers
Andrea–
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.Ing. Andrea Aime
@geowolfTechnical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Thu, Dec 6, 2012 at 7:09 AM, Christian Mueller <mcrmcr21@anonymised.com>wrote:
Hi Andrea
2012/12/6 Andrea Aime <andrea.aime@anonymised.com>
On Thu, Dec 6, 2012 at 2:04 PM, Christian Mueller <mcrmcr21@anonymised.com>wrote:
Hi Justin
The GSIP-82 patch requires a new section in
http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html
If this is not possible between 2.2.x versions, the backport is not
possible. Please tell me.The criteria is simple. Assuming 2.2.3 has the fix, can someone
edit the data directory with it, decide someone is off, and go back to
2.2.2, and have 2.2.2 still
be able to open it without problems?No. I think this the sudden death of the backport discussion :-).
I will focus on 2.3.x and stop bug fixing concerning filter chains in
2.2.x.CAS will also work starting with 2.3.x. Can somebody stop the publishing
of the CAS 2.2.x extension to the download page.Sure, removed from download page and won't generate artifacts as part of
the build anymore.
Cheers
ChristianBtw, backport wise, it's getting late, the window for backports
is closing today, 15 days from the release as per our recent discussion
on backports, though 1-2 days
off it won't be the end of the world (at least for me).Cheers
Andrea--
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.Ing. Andrea Aime
@geowolf
Technical LeadGeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549http://www.geo-solutions.it
http://twitter.com/geosolutions_it-------------------------------------------------------
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.