Opened 12 years ago
Closed 12 years ago
#1070 closed enhancement (fixed)
Improved security
| Reported by: | fxp | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | v2.10.0 RC0 |
| Component: | General | Version: | v2.8.0RC0 |
| Keywords: | Cc: |
Description
Change History (3)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
proxy tickets are a requirement for Geonetwork. The project that is funding this requires proxy ticket support so it will be there. Maybe not first commit but in very short order.
comment:3 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Merged on to trunk. Commit bffdb0192c9e8cd933a921b3cf71c984499c3768
https://github.com/geonetwork/core-geonetwork/commit/bffdb0192c9e8cd933a921b3cf71c984499c3768
Note:
See TracTickets
for help on using tickets.
Hi all, I am GeoServer developer working on the new GeoServer security subsystem which will support CAS. I read this proposal
http://trac.osgeo.org/geonetwork/wiki/proposals/SpringSecurity
and want to add some comments. It would be nice if Geonetwork could deal with CAS proxy tickets. The idea is that Geonetwork generates a proxy ticket for GeoServer, includes the proxy ticket in the GeoServer query string and GeoServer is able to authenticate the request. At the end of the day, we could have a single sign on solution.
I already integrated proxy tickets into GeoServer, if there is interest from your side, I am sure I can assist here to hurry up development.