Hi Matt,

Are you able to login with an end user's credentials? Is this problem only with logging in as an application user?

Are you using the following soap envelope in your request?
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"

Are you using the WSDL from the CUP 8.6.3 server? Do not use an old WSDL if you've updated CUP server.

Thanks,
Adrienne

Hi guys,

I get the same result when the log in request uses an enduser's credentials.

The SOAP envelope is correct and I loaded the WSDL from http://cupstest1:8082/presence-service/soap?wsdl

Full request/response:

<?xml version="1.0" encoding="http://www.w3.org/2003/05/soap-envelope"
standalone="no"?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Body>
<login xmlns="urn:cisco:cup:presence:soap" force='1'>
<username>axltest</username>
<password>axltest</password>
</login>
</soapenv:Body>
</soapenv:Envelope>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cup="urn:cisco:cup:presence:soap">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<SOAP-ENV:Code>
<SOAP-ENValue>SOAP-ENV:Sender</SOAP-ENValue>
</SOAP-ENV:Code>
<SOAP-ENV:Reason>
<SOAP-ENV:Text>Failed to login user</SOAP-ENV:Text>
</SOAP-ENV:Reason>
<SOAP-ENVetail>
<description xmlns="urn:cisco:cup:presence:soap">
<code>114</code>
<message>Failed to login user</message>
<fix>Ensure the login data is valid</fix>
</description>
</SOAP-ENVetail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>



Per my original post I have tried using both "CUP Super Users" and "Admin 3rd Party API" which of these is correct? In my testing both yielded the same result.



I don't see any activity in these logs when submitting my request, only the the errors in:

admin:file tail activelog epas/trace/esp/sdi/esp00000012.txt

Thanks,
Matt

Looks like I may be set here for now!

The validappusers query only returned one result which was the account which belonged to "Admin 3rd Party API" (and not the other account in CUP super users). I reset the password for this account, resubmitted the request and got a session key back.

I would also note FTR that application user accounts don't appear to become valid on changing to the correct group. I moved the account which had been in "CUP super users" into "Admin 3rd Party API" and re-ran the sql query and found it was still not listed as valid. I then reset the password, re-ran the sql query and saw it appear.

Thanks both for your help.

Thanks again for your help Jose, the detail is much appreciated.

Hi Kelvin,
Those queries are related to the inmemory datastores which has changed slightly with CUP release 8.6.4 & above. If using 8.6.4 & above try the following.
run pe sql ttroute select * from validappusers
run pe sql ttroute select * from validendusers
Regards,
Jose

Do refer developer guide. Has the app user been added to 'Admin 3rd Party API" group? 

Looks like there could be a problem. PLease raise a TAC case for further investigation.