User Management

RE: GetSite : Response Validation Error

2013-05-16T16:37:37Z

On the code samples page of this portal, there is a link on the right side of the page to an XML debug html file that allows you to submit a raw XML request and see the response. The response you are getting appears to be an issue with how your code handles the character encoding or some other code issue.

RE: GetSite : Response Validation Error

2013-05-16T13:22:33Z

Hi Nathan, Thanks! for the Reply I did try as suggested to access the GetSitr API, but i am getting response in Junk Values like below "?c???????????????????????????????????????????????????????????????????????????????????" I am able to succesfully get response from API GetUser, CreateMeeting, GethosturlMeeting and LstsummaryMeeting API from my C++ aplication. I am not able to get API GetSite and lstTimeZone working. I am currently using "xml_api_5 9.pdf" document as my reference, please update me if this is not the latest document. Thanks & Regards, Prabodh

RE: Is their any way to Validate XML Service URL ?

2013-05-15T17:17:17Z

Hello, You can establish a connection to the XML service URL wihtout a request to check for HTTP 200 success. If you are also checking authentication details, you can use a request like GetAPIVersion or GetlogInurlUser.

RE: GetSite : Response Validation Error

2013-05-15T17:12:38Z

[color=#525252]Hello,[/color] [color=#525252] [/color] [color=#525252] The error suggests that you are setting returnSettings as a child of body when it should be a child of bodyContent. I was able to test this request with returnSettings successfully. The reference guide is fairly old and will be updated, spelling errors, including returnSetting, should be addressed before a new guide is released.[/color] [color=#525252] [/color] [color=#525252][/color] [color=#525252][/color] [color=#525252]

[/color] [color=#525252] [/color] [color=#525252] removed[/color] [color=#525252] removed[/color] [color=#525252] removed[/color] [color=#525252] removed[/color] [color=#525252] [/color] [color=#525252]

[/color] [color=#525252] [/color] [color=#525252] [/color] [color=#525252] [/color] [color=#525252] TRUE[/color] [color=#525252] [/color] [color=#525252] [/color] [color=#525252] [/color] [color=#525252][/color]

Is their any way to Validate XML Service URL ?

2013-05-15T13:36:01Z

Is their any way to Validate XML Service URL ? any API ? Thanks & Regards, Prabodh

GetSite : Response Validation Error

2013-05-15T10:00:13Z

Hi, When i make a GetSite request

hostid hostpassword 0000 9999 johnsmith@xyz.com

true i always get a reponse "validation: unable to find FieldDescriptor for 'returnSettings' in ClassDescriptor of body" FAILUREvalidation: unable to find FieldDescriptor for 'returnSettings' in ClassDescriptor of bodyPRIMARY999999 Please can anyone help on this ? Plus I see mismatch in the request string tagname for the element ID "returnSettings", please correct on this. Thanks & Regards, Prabodh

RE: LstsummaryUser responds with error "Failed to get SiteUrl"

2013-04-25T16:12:33Z

Hello, WebEx is a hosted solution but you can host your API integration from wherever you choose. API is capable of creating and managing user accounts, creating and managing scheduled sessions, starting and joining sessions, and retrieving usage reports. You could use these features to build a custom portal on premise that could be used in place of the WebEx user interface. The in meeting experience would still be hosted.

RE: LstsummaryUser responds with error "Failed to get SiteUrl"

2013-04-25T07:37:44Z

[color=#222222]Thank you Nathan - much appreciated. I have tested on a dedicated development test site and everything works. However, I installed a Cisco Webex Meetings Server that is currently running a trial license. Will the Gold Developer Programme enable sites somehow on my local server. I would like to know the capabilities of the on-premise solution re XML API. The cloud-based solution works fine.[/color]

Free cloud-based AD integration and SAML SSO for WebEx Enterprise

2013-04-24T17:49:45Z

Hi everyone, I know that many companies who are looking to implement WebEx want to integrate with their Active Directory or LDAP server. OneLogin's free option allows you to do just that. Our AD and LDAP Connectors can be installed in minutes with no firewall changes required and setting up SSO to WebEx also just takes a couple of minutes. You can see the steps required below. [url=https://onelogin.zendesk.com/entries/362606-Configuring-SAML-for-WebEx]https://onelogin.zendesk.com/entries/362606-Configuring-SAML-for-WebEx[/url] OneLogin also supports user provisioning into WebEx on the paid plans. Here are some of the feature highlights: * Real-time user sync from AD * Automated provisioning and de-provisioning of users in WebEx * SAML-based single sign-on * Integration with Windows Integrated Authentication * Protect access with multi-factor authentication and IP address restriction * 99.99% uptime guarantee If you are interested in hearing more or would like assistance with this, please reach us at [url=mailto:support@onelogin.com]support@onelogin.com[/url]. The OneLogin Team

RE: LstsummaryUser responds with error "Failed to get SiteUrl"

2013-04-24T17:15:14Z

[color=#525252]Hello,[/color] [color=#525252] [/color] [color=#525252] The security context includes username, password, site id, and partner id. The site id and partner id reference the site you are working with. Without the site id and partner id, the site URL cannot be determined by the XML service. If you are using the API trial site, apidemoeu.webex.com, you can find the site id and partner id within this web portal (also listed below). If you are developing on your own WebEx enterprise account, your WebEx account manager or sales representative can help start the process of adding the Gold Developer Program to your account, if not already done. The Gold Developer Program will enable APIs and provide a separate dedicated test site for development. Your account manager will be able to provide site id and partner id once APIs are enabled on your site. It is also a best practice to include your header section near the beginning of your XML request, before body. [/color] [color=#525252] [/color] [b]Site URL[/b][color=#525252][b]: [/b] https://apidemoeu.webex.com[/color] [b]SiteID[/b][color=#525252][b]:[/b] 243585[/color] [b]PartnerID[/b][color=#525252][b]:[/b] g0webx![/color] [b]XML Service URL[/b][color=#525252][b]:[/b] https://apidemoeu.webex.com/WBXService/XMLService[/color][color=#525252][/color]

LstsummaryUser responds with error "Failed to get SiteUrl"

2013-04-24T16:03:14Z

I am sending the request in the attached request.xml. The response I get is in the attached response.xml file. I am interacting with a standalone/on-premise WebEx server that is running a free trial license. Any idea what I could be doing wrong?

RE: Register Attendee (to Waitlist)

2013-04-16T19:02:33Z

Hello, API does not support registration wait list. If you are building your own registration portal, it would be possible to build your own wait list functionality within your portal, allowing you to register the first attendee on the list if anyone deletes their registration from your portal.

Register Attendee (to Waitlist)

2013-04-16T18:48:58Z

Hey there, so I have my training session set to require registration, auto-approve registrations. I have 2 spots available but I have the waitlist feature enabled and to automatically register first attendee in waitlist. Logically I have all my ducks in a row. But when I go ahead and try to register in my application to a full training session it won't waitlist the registrant in Webex. I get back the message "The maximum number of registrants for this WebEx training has been reached " Which is true, but I thought the whole purpose behind the wait list is to wait list registrants after the maximum seat count has been reached. What am I missing?

RE: SetUser request returns an emptty string

2013-04-03T16:06:02Z

Confirmed fix on our dev servers. Thanks Jayde!

RE: SetUser request returns an emptty string

2013-04-03T15:55:04Z

John/Dylan, Just wanted to let you know that the issue has been patched in our development environment. I confirmed that using "application/x-www-form-urlencoded" works fine now as it did previously. Regards, Jayde

RE: SetUser request returns an emptty string

2013-03-28T18:48:17Z

Great. Thanks Jayde.

RE: SetUser request returns an emptty string

2013-03-28T18:44:35Z

@ John, This was an unforeseen issue which had resulted from a backend platform change. Generally API changes themselves are communicated out to customers. Unfortunately in this case it was not directly related to an API change itself but ended up affecting API requests in our development environment. @ Dylan, There is no ETA at this time but Engineering is looking into this as an urgent matter. They are well aware that moving this same change into Production will result in customer impact and have put a hold on making the same change in Production. The end goal is to correct this on the WebEx side so no intervention is required from the customer and it continues to function as it did on the previous platform. Regards, Jayde

RE: SetUser request returns an emptty string

2013-03-28T14:25:07Z

Any ETA on when this will be fixed? I'm not sure if this is the cause of our error yet, but if it is, we already have a large number of applications out on production that would be very difficult for us to safely modify in short time frame if this stops working on our production webex. Thanks!

RE: SetUser request returns an emptty string

2013-03-28T12:06:54Z

Thankyou Jade, that has cleared up the issue. Is there visibility to changes like this that WebEx makes to the test servers that we developers can see? This has caused me to waste a lot of time... John

RE: SetUser request returns an emptty string

2013-03-26T22:55:46Z

Hi John/Dylan, Can you check the Content Type you have set in the header of your request? We did just recently notice some issues with requests in our dev environment when Content Type is set as [i]application/x-www-form-urlencoded[/i]. If you change this to [i]application/xml[/i] then it should work. We're still looking into the change internally but modifying the Content Type should correct this in the meanwhile. Regards, Jayde Moors WebEx API Developer Services