Ticket #881 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Remote Greenstone 3 fails unable to access already open Derby DB

Reported by: ak19 Owned by: ak19
Priority: moderate Milestone: 3.06 Release
Component: Greenstone3 Runtime Severity: major
Keywords: Cc:


Fixed. Changeset: http://trac.greenstone.org/changeset/28958

Remote Greenstone 3 user authenticaton stopped working, because the code working with the DerbyWrapper? had changed, and now gliserver.pl could no longer instantiate another JVM that would access the Derby DB (via the users2DBtxt.java) when wanting to check if a user authenticates. Instead, a new GS3 service has been written, Authentication.remoteAuthentication(). This is called from the authentication-ping system action URL that the new ServletRealmCheck?.java pings when it is called by gliserver.pl

Change History

Changed 6 years ago by ak19

  • status changed from new to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.