cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1067
Views
0
Helpful
2
Replies

Presence API Authentication

dansmith110
Level 1
Level 1

We are attempting to integrate the presence API into a custom directory application displaying a user's presence. I've read through the Developer Guide on how to accomplish this and we're running into an issue with logging in an app-user.

I've tried numerous combinations of the username:pw by calling both of the following per the developer guide through Postman. The following calls are going against https://{cup-hostname:port}/presence-service and over HTTPS.

PUT /presence-service/users/{app-userid}/session

POST /presence-service/users/{app-userid}/sessions

I've also attempted to call the login method via SOAP with the wsdl and receive the same results. In both instances this is the response...

<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>

We have tried to change the password of the user and we're sure the credentials are correct. We've also tried to bump up permissions to highest we know of and still receive the same "Failed to login user" message. If I try to make a call against "getPolledPresence" without the required session key I receive a message stating the key is missing.

Are there any type of special permissions an app-user needs to authenticate against the API? Or does the app-user need to be created in a specific way to make this work? Is there any place we could check that a user needs to be in the admin panel for this to work?

Thanks!

2 Replies 2

nathan.a.reeves
Level 1
Level 1

Hey Dan,

Done similar (using the SOAP API) to get presence info out.  Off the top of my head, just double check the app-user is a member of 'Third Party Application Users' and 'Admin-3rd Party API'.  Suspect it's the latter that may get things going for you.

Let us know whether this changes anything.

Nathan

Hi Nathan,

Thanks for the tip! After some more testing we are able to retrieve a session-key (from our secondary presence server). We're looking into the configuration of the main server now, but for the time being the issue of failing to authenticate seems to be resolved.

Thanks,

Dan