#1 2011-09-08 13:53:13

**_wsipc-mike_**

Call principal-list via API call

I thought I have this working, but found that this morning inexplicably stopped working -- giving a 'no-login' error. A little digging and I found that I could only get it to work via API/XML calls if I logged in via the web UI first.

My server is on-premise and I think I am following the directions properly (http://help.adobe.com/en_US/connect/8.0 … 5-7ff8_SP1).

Here is the process I am going through:

I start here to get my cookie:

https://my.connect.server/api/xml?action=common-info

Getting:

<results>
<status code="ok"/>
<common locale="en" time-zone-id="85">
<cookie>my-cookie</cookie>
<date>2011-09-08T18:31:23.943+00:00</date>
<host>https://my.connect.server</host>
<local-host>my-connect-server</local-host>
<admin-host>my.connect.server</admin-host>
<url>/api/xml?action=common-info</url>
<version>8.0</version>
<account account-id="7"/>
<user-agent>
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.218 Safari/535.1
</user-agent>
</common>
</results>

Then I log in using the same session ID:

https://my.connect.server/api/xml?actio … =my-cookie

I get:

<results>
<status code="ok"/>
<users>
<user user-id="10013" account-id="7">
<name>Enterprise Account</name>
<date-expired>3000-01-01T00:00:00.530+00:00</date-expired>
</user>
</users>
</results>

But then I try:

https://my.connect.server/api/xml?actio … =my-cookie

I get nothing but this:

<results>
<status code="no-access" subcode="no-login"/>
</results>

Am I missing a step here?

Last edited by **_wsipc-mike_** (2011-09-08 13:54:24)

**_catholicon_**

Re: Call principal-list via API call

I think you need to use action=login for logging in e.g.
https://my.connect.server/api/xml?action=login&login=me@login.org&password=MyPassword&session=my-cookie

**_wsipc-mike_**

Re: Call principal-list via API call

Thanks, that did the trick. Not sure why I didn't see that myself since that's exactly how it is in the documentation. Since it seemed I was getting a successful login (in my 2nd step) I never looked there.