search

jasonramsden / php-ews

Automatically exported from code.google.com/p/php-ews
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Request always returns null #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Really impressed with this project. Great work. I've got it working on my dev 
server (WAMP stack)...but when I move it to my production (LAMP) Debian server 
I get nothing but a NULL result for any of the function calls. I might be 
missing something basic...I'm sure it's a configuration issue on my end...some 
kind of error would be helpful....any ideas on where I could start with 
troubleshooting??? Do I need to COM objects enabled, etc..? Any more info on 
the dependencies would be really great.

Original issue reported on code.google.com by storypro...@gmail.com on 11 Jul 2011 at 11:14

GoogleCodeExporter commented 9 years ago 
You are probably missing either cURL or SOAP for PHP

Original comment by torbenko...@gmail.com on 29 Sep 2011 at 5:46

GoogleCodeExporter commented 9 years ago 
I have both cURL and SOAP for PHP but always get a null as well

Original comment by frak....@gmail.com on 29 Sep 2011 at 8:13

GoogleCodeExporter commented 9 years ago 
The problem is that you are likely receiving a 401 Unauthorized response back 
php-ews is not handling that properly. It appears that the options that cURL is 
compiled with in Debian (as well as Ubuntu and probably other Debian based 
distros) has changed. I'm going to try to compile from source and see if I can 
get it working.

Original comment by JamesIArmes@gmail.com on 29 Sep 2011 at 10:29

GoogleCodeExporter commented 9 years ago 
Having done some investigation since your post, it does indeed seem that the 
account I was using did not have the correct permissions to access everyone's 
mailbox.  Sorry for the misleading post.

Original comment by frak....@gmail.com on 29 Sep 2011 at 10:32

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
In order to fix the issue with the version of cURL currently provided in Debian 
in Ubuntu, you will need to compile from source using the following to 
configure (you may have to provide additional options if you have other 
requirements):

./configure --enable-http --enable-ftp --enable-file --enable-telnet 
--enable-tftp --enable-ipv6 --enable-crypto-auth --enable-tls-srp 
--enable-cookies

This has been tested with cURL 7.22 on Ubuntu 10.04 (Lucid Lynx).

Original comment by JamesIArmes@gmail.com on 29 Sep 2011 at 11:17

GoogleCodeExporter commented 9 years ago 
Marking this as "WontFix" since it is not actually an issue with the library.

Original comment by JamesIArmes@gmail.com on 29 Sep 2011 at 11:18

GoogleCodeExporter commented 9 years ago 
To verify that your curl setup is working you can run the following from the 
command line (make sure you replace *host*, *username* and *password* with the 
appropriate values):

curl https://*host*/EWS/Exchange.asmx -w %{http_code} --ntlm -u 
*username*:*password* -k

If curl is configured correctly, this should return a 302 rather than a 401.

Original comment by JamesIArmes@gmail.com on 22 Nov 2011 at 1:18

GoogleCodeExporter commented 9 years ago 
ok, i'm on unbuntu 10.04
if installed the build-dep's for curl with apt-get build-dep curl
downloaded the sources
wget http://curl.haxx.se/download/curl-7.23.1.tar.gz
extracted them and configured with your line

i get:

checking whether to enable the threaded resolver... no
checking whether to enable verbose strings... yes
checking whether to enable SSPI support (Windows native builds only)... no
checking whether to enable cryptographic authentication methods... yes
checking whether to enable NTLM delegation to winbind's helper... yes
checking whether to enable TLS-SRP authentication... yes
checking whether to enable support for cookies... yes
checking whether to enable hidden symbols in the library... no

but then i get:

  curl version:    7.23.1
  Host setup:      x86_64-unknown-linux-gnu
  Install prefix:  /usr/local
  Compiler:        gcc
  SSL support:     enabled (OpenSSL)
  SSH support:     no      (--with-libssh2)
  zlib support:    enabled
  krb4 support:    no      (--with-krb4*)
  GSSAPI support:  enabled (MIT/Heimdal)
  SPNEGO support:  no      (--with-spnego)
  TLS-SRP support: no      (--enable-tls-srp)
  resolver:        default (--enable-ares / --enable-threaded-resolver)
  ipv6 support:    enabled
  IDN support:     enabled
  Build libcurl:   Shared=yes, Static=yes
  Built-in manual: enabled
  Verbose errors:  enabled (--disable-verbose)
  SSPI support:    no      (--enable-sspi)
  ca cert bundle:  /etc/ssl/certs/ca-certificates.crt
  ca cert path:    no
  LDAP support:    enabled (OpenLDAP)
  LDAPS support:   enabled
  RTSP support:    enabled
  RTMP support:    no      (--with-librtmp)
  Protocols:       DICT FILE FTP FTPS GOPHER HTTP HTTPS IMAP IMAPS LDAP LDAPS POP3 POP3S RTSP SMTP SMTPS TELNET TFTP

so it will compile without TLS-SRP, google told me that openssl hasn't tls-srp 
support... is it needed?

if i compile it anyway i still get the the 401 error

what have you done?

Original comment by mr.schic...@gmail.com on 22 Nov 2011 at 4:32

GoogleCodeExporter commented 9 years ago 
@mr.schickfick are you still having trouble with this? I have not tested this 
method using cURL 7.23.1. You can get cURL 7.22.0 (which is what I used above) 
from http://curl.haxx.se/download/curl-7.22.0.tar.gz.

Original comment by JamesIArmes@gmail.com on 6 Jan 2012 at 1:49

GoogleCodeExporter commented 9 years ago 
hey, i have exactly the same problem, the code in #8 returned 401

Original comment by icks...@googlemail.com on 6 Jan 2012 at 3:58

GoogleCodeExporter commented 9 years ago 
same as #11. If we're getting a 401 return to 

curl https://*host*/EWS/Exchange.asmx -w %{http_code} --ntlm -u 
*username*:*password* -k

but can use those same credentials to log into https://*host*/owa without a 
problem, where should we look next?

Original comment by Zxur...@gmail.com on 27 Jan 2012 at 4:15

GoogleCodeExporter commented 9 years ago 
Any help on this? I have 2 CentOS servers. It works on one but not the other. I 
don't see much of a difference. Maybe a different in curl versions?

Original comment by ke...@keithslater.com on 1 Feb 2012 at 3:44

GoogleCodeExporter commented 9 years ago 
From what I can tell it is definitely a problem with what curl version is being 
used. It looks like somewhere between 7.15.5 and 7.19.7 curl started using NSS 
for SSL instead of OpenSSL. From what it looks like curl 7.20.1 or above should 
fix the problem however I'm having a hard time upgrading.

Relevant info:
https://bugzilla.redhat.com/show_bug.cgi?id=603783

Original comment by ke...@keithslater.com on 1 Feb 2012 at 4:41

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hi,

yes still issues, again with 7.22.0 same error:

curl-7.22.0# ./configure --enable-http --enable-ftp --enable-file 
--enable-telnet --enable-tftp --enable-ipv6 --enable-crypto-auth 
--enable-tls-srp --enable-cookies | grep -i SRP
checking for SRP_Calc_client_key in -lcrypto... no
checking whether to enable TLS-SRP authentication... yes
  TLS-SRP support: no      (--enable-tls-srp)

Original comment by mr.schic...@gmail.com on 13 Feb 2012 at 8:59

GoogleCodeExporter commented 9 years ago 
This issue has been moved to GitHub 
https://github.com/jamesiarmes/php-ews/issues/11

Original comment by JamesIArmes@gmail.com on 14 Feb 2012 at 3:01