Uploading Files for Cloudera Support - alternate method

[#1]

For users experiencing trouble uploading a file to a case using the standard ‘UPLOAD FILE(s)’ method from the Case Attachment tab, the following alternatives exist:

Upload files from the command line

30GB Limit

This method utilizes a java program to allow case attachments to be uploaded via the command line. This method is intended for those who are experiencing trouble with the case attachment UI or who prefer to upload a file from the command line.  This method also supports proxy parameters

How to use:

• Download the JAR
• Run the program:

  Usage: java -jar cloudera.attachment.cli.jar [case_number] [email_address] [file_name...]

  Example:  java -jar cloudera.attachment.cli.jar 55555 [email protected] logs1.log logs2.log

  The above example uploads logs1.log and logs2.log to case number 55555 from [email protected]

  Supported proxy command line properties include:  -Dhttp.proxyHost=, -Dhttp.proxyPort=, -Dhttp.proxyUsername=, -Dhttp.proxyPassword=

  Example: java -jar -Dhttp.proxyHost=192.x.x.x -Dhttp.proxyPort=8080 cloudera.attachment.cli.jar 55555 [email protected] logs1.log

Please Note:

When the Java app connects to the server, the server presents a digital certificate. The app checks this certificate against a list of trusted authorities in a file called a TrustStore. If the certificate's issuer is in the TrustStore, the connection proceeds. The issue arises when your organization uses internal services with certificates that aren't from a public, globally recognized Certificate Authority (CA). In these cases, you have to manually tell the app to trust the certificate.

Method 1:
This approach involves modifying the default, system-wide TrustStore file that comes with the Java Development Kit (JDK).

Method 2:
Specify a truststore for each invocation

e.g. java -Djavax.net.ssl.trustStore=/path/to/myTruststore.jks -Djavax.net.ssl.trustStorePassword=yourPassword . . .