All,
I may just be showing my nievete about gSearch, but I discovered what
configuration parameters were necessary for the
command line calls to work with my fedora instance secured through https. My
configuration involved installing the
fedoragsearch.war file on the same tomcat instance that fedora was running on -
I'm fairly certain that this made things
easier.
In the ../repository.properties files for gsearch:
.
.
.
fgsrepository.fedoraSoap =
https://localhost:<https-port>/fedora/services
fgsrepository.fedoraUser = <fedora user>
fgsrepository.fedoraPass = <fedora psw>
.
.
.
fgsrepository.trustStorePath =<path to fedora server truststore>
# I added, then removed the fgsrepository.trustStorePass = parameter -
it seemed to be a culprit in the failure.
Command-line calls to the gsearch scripts now seem to be processing correctly.
hth,
-Tim
> -----Original Message-----
> From: Tim Cornwell [mailto:[email protected]]
> Sent: Friday, August 13, 2010 1:19 PM
> To: [email protected]
> Subject: [fcrepo-user] gSearch command line call failure
>
> Hello all,
>
> Thanks much - in advance.
>
> I am trying to use the command-line client calls to gsearch.
> When I submit the command:
>
> sh runRESTClient.sh "http://localhost:8843/fedoragsearch/rest
> updateIndex #"
>
> The client code asks for a user & password (which I supply
> with my fedora repository uid/psw - not sure if this is correct)
> The client then returns:
>
> Args
> 0=https://localhost:8843/fedoragsearch/rest
> 1=updateIndex
> 2=#
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building
> failed:
> sun.security.provider.certpath.SunCertPathBuilderException:
> unable to find valid certification path to requested target
> at
> com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl
> .java:1623)
> at
<snip>
> java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
> at
> sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:289)
> ... 19 more
>
>
> I am at a loss to know what sort of security violation this
> is talking about.
>
> Any help is greatly appreciated.
>
> Thanks,
> -Tim
>
> Timothy Cornwell, Programmer/Analyst
> National Science Digital Library
> http://nsdl.org
>
>
> --------------------------------------------------------------
> ----------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Fedora-commons-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
