Ignore:
Timestamp:
2012-09-18T18:10:37+12:00 (12 years ago)
Author:
ak19
Message:

Fixes to get Remote Greenstone 3 working with client-gli: 1. client-GLI should not start the local GS3 server, since client-GLI will be running against a remote server. 2. The encryption process for authentication had been changed for GS3, so now Authentication.java has a main function which is invoked by gliserver's gsdlCGI.pm to encrypt the password. 4. UsersDB when converted to txt for parsing by gliserver.pl has a different structure, so gliserver.pl needs to take that into account. 5. util.pm's functions for prepending and appending to environment variables needs to use an OS dependant path separator. This was not noticed when testing the remote GS server on 32 bit linux so far, but the windows style path separator (semicolon) used so far didn't work on the 64 bit linux test machine.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/trunk/greenstone3/src/java/org/greenstone/gsdl3/service/Authentication.java

    r25852 r26206  
    10371037        return collect_list_node;
    10381038    }
     1039
     1040    // main() method - calls hashPassword() on any String argument, printing this to stdout
     1041    // This main() is invoked by gliserver.pl perl code to encrypt passwords identically to Java code.
     1042    public static void main(String[] args) {
     1043    if(args.length < 1) {
     1044        System.err.println("Usage: Authentication <string to encrypt>");
     1045        System.exit(-1);
     1046    }
     1047    // just hash the first argument
     1048    String hash = Authentication.hashPassword(args[0]);
     1049    System.out.println(hash);
     1050    }
    10391051}
Note: See TracChangeset for help on using the changeset viewer.