Allowing users to login to view or use additional resources will be a very common operation with all the rich functionality that GeoExt exposes. This work item seeks to establish some default components and best practices for people building applications that require some sort of login.
It should be a very flexible component, as there are lots of ways to have users login. It should support a number of backends - http basic and digest, open id, geoxaml etc. And should provide an easy programming model to plug-in to other authentication mechanisms.
A default GUI component will also be provided, to allow people to easily add authentication. But since there are many different workflows that might want to handle it differently, the GUI component should be built for flexibility.
Funding
This roadmap item is currently unfunded.
Add your support for this item by contacting us for a quote and discussion of the particular features you need.
Get a quote now!
Get a quote or read more about core development to add your support to a road-map item.
Other Roadmap Items
Many applications will need to allow users to logon to a remote server, be it for remote administration, editing of data, or controlled view access. GeoExt should have a default manager for logging on, with different options for the backend login mechanism and desired front-end gui dialog.
GeoExt should provide components that make it easy to export the current map to a variety of formats. Foremost among these is embedding the current view to a webpage or blog. Past that it would be great to export in a variety of formats, like Google Earth, PDF, or as another GeoExt application with alternate controls.
Web users especially require a flexible library of images for their map styles. We fill this need with an improved Image Manager for our Styler application.