Solved: Null pointer response when requesting user (user management API)

gmorgan · ‎07-19-2017

Previously when calling out to the api to determine if a user existed we would get a empty response when the user couldn't be found. Now we are receiving a NullPointer.

I presume this is not intended behavior.

Q: Does anyone know when this will be addresses?

Request

https://pingidentity-dev.webex.com/WBXService/XMLService

<?xml version="1.0" encoding="UTF-8"?>

<webExID>adminusername</webExID>

<password>adminpassword</password>

</securityContext>

</header>

<body>

<use:email>gmorgan@pingidentity.com</use:email>

</bodyContent>

</body>

</message>

Response

<?xml version="1.0"?>

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:use="http://www.webex.com/schemas/2002/06/service/user">

<serv:header>

<serv:response>

<serv:result>FAILURE</serv:result>

<serv:reason>validation: Null Point Error</serv:reason>

<serv:gsbStatus>PRIMARY</serv:gsbStatus>

<serv:exceptionID>000000</serv:exceptionID>

</serv:response>

</serv:header>

<serv:body>

<serv:bodyContent/>

</serv:body>

</serv:message>

mifierro · ‎07-20-2017

Hi Glen! I apologize for the inconsistent behavior you are seeing. This is basically an issue with the XML API V9.0, which is running on pingidentity-dev.webex.com. Current versions of the XML API correct this. I used your API request on a test site running XML API v11.0 SP3, and a much more descriptive message is returned

<serv:response>

<serv:result>FAILURE</serv:result>

<serv:reason>Sorry, no record found</serv:reason>

<serv:gsbStatus>PRIMARY</serv:gsbStatus>

<serv:exceptionID>000015</serv:exceptionID>

</serv:response>

When your site is upgraded onto V10.x or V11.x, you will not receive the null pointer exceptions.

--

Michael Fierro ● .:|:.:|:.

Customer Support Engineer

Cisco - API Developer Services

mifierro@cisco.com

View solution in original post

mifierro · ‎07-20-2017

Hi Glen! I apologize for the inconsistent behavior you are seeing. This is basically an issue with the XML API V9.0, which is running on pingidentity-dev.webex.com. Current versions of the XML API correct this. I used your API request on a test site running XML API v11.0 SP3, and a much more descriptive message is returned

<serv:response>

<serv:result>FAILURE</serv:result>

<serv:reason>Sorry, no record found</serv:reason>

<serv:gsbStatus>PRIMARY</serv:gsbStatus>

<serv:exceptionID>000015</serv:exceptionID>

</serv:response>

When your site is upgraded onto V10.x or V11.x, you will not receive the null pointer exceptions.

--

Michael Fierro ● .:|:.:|:.

Customer Support Engineer

Cisco - API Developer Services

mifierro@cisco.com

gmorgan · ‎07-21-2017

Thanks for the reply Michael.

How does one go about having the version bumped to 11?

Glen

mifierro · ‎07-21-2017

Contact your WebEx sales rep, they will be able to give you the information for upgrading.

nathanlangton · ‎07-28-2017

Hi Michael,

Our account was upgraded:

Service version: WBS32

Page version: 32.4.1.1

Client version: 32.4.1.3

However we still see the above error (<serv:reason>validation: Null Point Error</serv:reason>) in our response. We have also had customers reach out with the same issue.

From what we can tell with our test accounts, this issue started on July 2'nd.

mifierro · ‎07-28-2017

I just followed up with our engineers, this issue had been fixed for API version 11.x, but a regression to the old behavior (returning the Null Point Error) was found earlier this month. It appears that a fix has just been checked in, but I don't have an ETA yet on when that fix will be pushed out to sites.

--

Michael Fierro ● .:|:.:|:.

Customer Support Engineer

Cisco - API Developer Services

mifierro@cisco.com

nathanlangton · ‎07-31-2017

Thanks Michael,

Keep us posted on the ETA. We have some joint customers unable to use our integration with WebEx due to this issue.

nathanlangton · ‎08-04-2017

Hi Michael,

Our automation has been successfully passing on our account for the last couple days. I assume the fix was pushed in.

Are there any specifics we could share with customers if they face this issue? What version should they update to or is this fix being applied access the board. Thanks!

kasutton · ‎08-04-2017

Hi Nathan,

If you're testing on BTS, that makes sense. We did roll out the fix to BTS on the night of 7/31, but it will not begin rolling out to production servers until 8/9. According to documentation, the fix is in all XML versions (8/9/10/11).

Kasey Schultz

API Developer Services - WebEx - Cisco Systems, Inc..:|:.:|:.