Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-28-2006, 12:21 AM
Junior Member
 
Posts: 9
Default The last word in where to send SOAP requests...!

Hello,

I am in the process of getting SOAP requests to work with a zimbra installation for automated account provisioning. At first, by looking at the soap.txt file, I was under the impression that these requests should be sent to http://servername/service/soap . When this didn't work, I soon found several posts on this forum saying to use https://servername:7071/service/admin/soap for the admin functions. Elsewhere I saw statements saying for non admin functions to use http://servername:7070/service/soap .

Needless to say, I am a bit confused as to where to begin. All of these produce various error messages, the original http://servername/service/soap producing "unknown document" errors while https://servername:7071/service/admin/soap currently producing curl_exec errors.

Basically, I am asking the good people here::

1) is http://servername/service/soap used for anything? how about http://servername:7070/service/soap?

2) if not, is https://servername:7071/service/admin/soap the correct url for ALL SOAP requests, admin or otherwise? and if so, how is it I can't find this information in either soap.txt nor soap-admin.txt?

3) finally, is there anywhere to configure this?

a massive thanks to anyone able to end my confusion! -Felix
Reply With Quote
  #2 (permalink)  
Old 06-28-2006, 08:06 AM
Zimbra Employee
 
Posts: 4,792
Default

http://servername/service/soap is for use requests (ie the web client type behavior or working with a individual user's mailbox.)

https://servername:7071/service/admin/soap Is for admin commands ie the things you can do in the admin UI or with an admin level auth token.

What is the exact SOAP you are sending? What response or error do you get back?
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #3 (permalink)  
Old 06-28-2006, 09:08 AM
Junior Member
 
Posts: 9
Default

I have been trying to use the PEAR::SOAP module (is there any recommended php module to use?), however the request it generates creates an 'ns4' namespace which may be having creating problems. I am currently just trying to send an auth request:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns4="urn:zimbra"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>

<ns4:AuthRequest>
<name xsi:type="xsd:string">admin@zimbra1.hr.net</name>
<password xsi:type="xsd:string">k9ad4BB2</password></ns4:AuthRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

----------------------------------------

This produces the error:
<br>An error #soap:Client occurred!<br> Error: unknown document: ns4:AuthRequest<br>
Reply With Quote
  #4 (permalink)  
Old 06-28-2006, 09:22 AM
Junior Member
 
Posts: 9
Default

ahhhh... i was using zimbra instead of zimbraAdmin as the namespace. Seems to have fixed the problem. One other question though - any time i want to send a "use" request to /service/soap do I first need to send an AuthRequest to the /service/admin/soap to get an authToken?

Last edited by felix; 06-28-2006 at 11:55 AM..
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.