cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

If your Cloud Collaboration question is not answered quickly, please email devsupport@webex.com for additional help

195
Views
5
Helpful
2
Replies
Highlighted

Error from webex meetings XML API - Failed to get SiteUrl when calling API with oauth authentication

My error is very similar to the following:

https://community.cisco.com/t5/collaboration-documents/failed-to-get-siteurl/ta-p/3621326

 

but in this case, the authentication mechanism is oauth.  I am also getting a failed to get SiteURL error, and unsure how to resolve.

 

----------------------

request

---------------------

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:serv="http://www.webex.com/schemas/2002/06/service" targetNamespace="http://www.webex.com/schemas/2002/06/service">
    <header>
        <securityContext>
          <webExID>##################</webExID>
          <webExAccessToken>*****************</webExAccessToken>
          <siteName>###########.webex.com</siteName>
        </securityContext>
    </header>
    <body>
        <bodyContent
            xsi:type="java:com.webex.service.binding.user.LstsummaryUser">
            <listControl>
                <serv:startFrom>1</serv:startFrom>
                <serv:maximumNum>1000</serv:maximumNum>
            </listControl>
        </bodyContent>
    </body>
</serv:message>

 

 

 

----------------

response

---------------------

<?xml version="1.0" encoding="UTF-8" ?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common">
<serv:header>
<serv:response>
<serv:result>FAILURE</serv:result>
<serv:reason>Failed to get SiteUrl</serv:reason>
<serv:gsbStatus>BACKUP</serv:gsbStatus>
<serv:exceptionID>010000</serv:exceptionID></serv:response>
</serv:header>
<serv:body>
</serv:body>
</serv:message>

 

 

 

2 REPLIES 2
Highlighted
Beginner

Not sure if you resolved this issue.  I'm using OAuth and the difference in my security context is we use the session ticket, not access token.  For the site name, try using just the value before .webex.com so if your site is https://companyname.webex.com just use companyname as your siteName.  Here is an example using Postman... I filter on date created...  

 

  <header>
              <securityContext>
         <webExID>email@domain.com</webExID>
         <sessionTicket>********this is obtained by using another call*********</sessionTicket>
         <siteName>nameofsite</siteName>
        </securityContext>
   </header>
   <body>
<bodyContent
            xsi:type="java:com.webex.service.binding.user.LstsummaryUser">
            <listControl>
                <serv:startFrom>1</serv:startFrom>
                <serv:maximumNum>10</serv:maximumNum>
                <serv:listMethod>AND</serv:listMethod>
            </listControl>
            <order>
                <orderBy>UID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
            <dataScope>
                <regDateStart>01/25/2021 01:00:00</regDateStart>
                <regDateEnd>01/30/2021 23:59:00</regDateEnd>
            </dataScope>
        </bodyContent>
   </body>
</serv:message>
Highlighted

Turns out the error was bad data in the siteName param in my soap envelope.
instead of .webex.com, it's just the part of the hostname as the soap param
Content for Community-Ad

This widget could not be displayed.