Appian WEB API Sessions

RE: Appian WEB API Sessions

PhilB — Fri, 14 Jul 2017 10:14:26 GMT

Could you make a call to https://<site url>/suite/logout ?

RE: Appian WEB API Sessions

sambhavj — Thu, 13 Jul 2017 08:38:10 GMT

We are also facing a similiar problem , while calling an Appian WEBAPI from javascript in the web browser , a session for basic user( HTTP BAsic AUth Credentials used t call the service ) is established and when you redirect to appian , you login with that basic user.
Can someone suggest how to overcome this problem

RE: Appian WEB API Sessions

Shyam Bommakanti — Tue, 23 May 2017 18:08:11 GMT

I'd like to know as well.

RE: Appian WEB API Sessions

PhilB — Tue, 23 May 2017 15:52:29 GMT

I'd be interested to know this as well. Given Web APIs use HTTP basic authentication, you'd expect them to behave as described here - en.wikipedia.org/.../Basic_access_authentication - ie there'd be a cache of some sort, but only for a maximum around 15 minutes.

Thinking about it, this would actually be relatively simple to test; just build a webAPI and call it from your browser. Enter the username and password requested, and view the result. Next, hit F5 to refresh the page. If you're prompted to enter the credentials then there's no caching, but if you aren't there's some caching somewhere - though it might be difficult to tell where. Maybe the browser debug tools could help there though?

RE: Appian WEB API Sessions

mohamedt808 — Tue, 23 May 2017 15:42:15 GMT

Its more sort of a question to understand if web API sessions will be considered in server as same as the user login session or they are different and short living sessions.

RE: Appian WEB API Sessions

Gaurav Arora — Mon, 22 May 2017 23:52:50 GMT

Please elaborate on your requirement.