Digital Media Suite API Forums

« Back to Show and Share API Forum

Testing API w/ Trial Account

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
I'm looking at writing a component to allow publishing of content to Show and Share.  I'd like to be able to test as I go.  I requested a trial account and downloaded the DMS API Tester.  I followed the instructions in the API documentation under "Checking the API Status".  I get a HTTP Status of 500 on the response.  Should I consider this a problem with the DMS API Tester or is the API not supposed to work with trial accounts?  Thanks.

RE: Testing API w/ Trial Account
api dms api testing trial
Answer
8/9/10 11:38 PM as a reply to Joe Domoto.
Hi Joe,
 
May I ask what the URL of the server you have the trial account on?  We are directly in charge of the trial accounts, but we'll look into this for you.
 
- Joe Y.
Digital Media Systems
 

[ deleted by administrator ]
 

I've successfully used addContent using my own code, so I'm considering this a tool issue until I run into a query type that fails.  

I also have problems with trial account. I'm developing application which uploads video file to Cisco Show & Share so I started playing with DMS API Tester tool. It works fine for getPublicCategories and getUserDetails requests but when I try addContent or getAccessTicket it returns HTTP status code 403. The same thing happens when I do it manually using curl tool. See below for sample conversation with Show & Share server. Does it mean that upload through DMS API is not available on trial account or maybe I'm doing something wrong?

* About to connect() to snssns3.xfactorcom.com port 8443
* Trying 4.79.155.42... connected
* Connected to snssns3.xfactorcom.com (4.79.155.42) port 8443
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSLv2, Client hello (1):
SSLv3, TLS handshake, Server hello (2):
SSLv3, TLS handshake, CERT (11):
SSLv3, TLS handshake, Server key exchange (12):
SSLv3, TLS handshake, Server finished (14):
SSLv3, TLS handshake, Client key exchange (16):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSL connection using EDH-RSA-DES-CBC3-SHA
* Server certificate:
* subject: /C=US/postalCode=07606/ST=NJ/L=South Hackensack/streetAddress=3 Empire Blvd./O=X-Factor Communications/OU=IT/OU=Secure Link SSL/CN=snssns3.xfactorcom.com
* start date: 2010-04-29 00:00:00 GMT
* expire date: 2011-04-29 23:59:59 GMT
* subjectAltName: snssns3.xfactorcom.com matched
* issuer: /C=US/O=Network Solutions L.L.C./CN=Network Solutions Certificate Authority
* SSL certificate verify ok.
* Server auth using Basic with user '***'
> POST /vportal/services/xml/api HTTP/1.1
> Authorization: Basic ***
> User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
> Host: snssns3.xfactorcom.com:8443
> Accept: */*
> Content-type: application/xml
> Content-Length: 639
>
> <xml-fragment xmlns:vp="http://model.data.core.vportal.cisco.com/vp_ns">
> <vp:vportal>
> <vportal_id>1</vportal_id>
> </vp:vportal>
> <vp:vprequest>
> <query>addContent</query>
> </vp:vprequest>
> <vp:vpcontent>
> <title>Title 1</title>
> <description>Description 1</description>
> <contentattribute>
> <key>addedDate</key>
> <value>1209407608</value>
> <namespace>com.cisco.vportal.1</namespace>
> </contentattribute>
> <live>false</live>
> <state>
> <contentstate>DRAFT</contentstate>
> </state>
> </vp:vpcontent>
> </xml-fragment>
< HTTP/1.1 403 Forbidden
< Server: Apache-Coyote/1.1
< errorMsg: Access Forbidden
< Content-Type: text/xml
< Content-Length: 0
< Date: Sun, 20 Feb 2011 15:08:48 GMT
* Connection #0 to host snssns3.xfactorcom.com left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):

The xfactor Show and Share trial site is not meant for testing API calls.