LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  HTTP Node Equivalent of wget --no-check-certificate for Sharepoint

    Employee
    Posted 07-02-2014 14:42

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: sdb

    I get a peer authentication error when I use an http node to GET a file from a URL to Sharepoint.

    To investigate I ran the same on the linux server command line using wget, and it turns out there is an Entrust certificate required for the server to retrieve the file, unless I use the "no-check-certificate" switch, in which case the absence of the certificate is ignored. I can then download the file using my credentials for Sharepoint.

    How can I get the http node to behave the same way and ignore the fact that the server has no certificate?

    The precise error is

    peer not authenticated
    Stack Trace:
    sun.security.ssl.SSLSessionImpl.getPeerCertificate s(SSLSessionImpl.java@407))
    org.apache.http.conn.ssl.AbstractVerifier.verify(A bstractVerifier.java@126))
    org.apache.http.conn.ssl.SSLSocketFactory.connectS ocket(SSLSocketFactory.java@437))
    org.apache.http.impl.conn.DefaultClientConnectionO perator.openConnection(DefaultClientConnectionOper ator.java@180))
    org.apache.http.impl.conn.ManagedClientConnectionI mpl.open(ManagedClientConnectionImpl.java@294))
    org.apache.http.impl.client.DefaultRequestDirector .tryConnect(DefaultRequestDirector.java@643))
    org.apache.http.impl.client.DefaultRequestDirector .execute(DefaultRequestDirector.java@479))
    org.apache.http.impl.client.AbstractHttpClient.exe cute(AbstractHttpClient.java@906))
    org.apache.http.impl.client.AbstractHttpClient.exe cute(AbstractHttpClient.java@805))
    com.lavastorm.brain.node.http.HttpNode.executeRequ est(HttpNode.java@443))
    com.lavastorm.brain.node.http.HttpNode.processAll( HttpNode.java@660))
    com.lavastorm.brain.execution.java.node.NodeWrappe r.nodeProcess(NodeWrapper.java@527))
    com.lavastorm.brain.execution.java.node.NodeWrappe r.run(NodeWrapper.java@769))
    com.lavastorm.brain.execution.java.node.NodeWrappe r.main(NodeWrapper.java@1466))

    Simon


  • 2.  RE: HTTP Node Equivalent of wget --no-check-certificate for Sharepoint

    Employee
    Posted 07-15-2014 08:13

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ltolleson

    Hi Simon,

    I apologize for the delayed response. Seems your post are missing a response. I will try to help.

    First, are you using the Sharepoint nodes that have been implemented in the LAL library or are you building your own using the base HTTP node?

    There are 3 different authentication methods for these nodes. Please let me know exactly how you are attempting to connect.

    Thanks,
    Larry


  • 3.  RE: HTTP Node Equivalent of wget --no-check-certificate for Sharepoint

    Employee
    Posted 07-17-2014 09:49

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: sdb

    Larry

    Thanks for picking this up.

    I was using the HTTP node, but I subsequently tried the Sharepoint Nodes - folder and download. All die with the same error "peer not authenticated", which seems to relate to not being able to verify the certificate - in this case Entrust.

    I overcame the wget --no-check-certificate by getting hold of the Entrust chain certificate, and although a Linux novice, managed to get this configured on to the server in such a way that I can now run wget without the switch - i.e. it automatically finds and verifies the Entrust certificate, and can download files from our Sharepoint server.

    However, despite stopping and restarting the server since the configuration change, I cannot get HTTP, or Sharepoint nodes beyond this point.

    How do these nodes verify certificates if not the same way as wget/openssl?

    Simon