We're having some trouble getting Coldfusion to talk to MS Exchange (SBS2003).
We have a working mail exchange and Web Access is configured in IIS and indeed we are able to login via Outlook Web Access (OWA).
After following the Adobe guidelines on configuring jrun to handle ssl connections and adding the cert to the keystore, CF returns the following error:
Could not login to the Exchange server.
Verify the server name, username, and password. Ensure that proper client certificates are installed.
<cfexchangeconnection action = "open"
connection = "myExchangeConnection"
server = "myservername.net"
port = "443"
username = "myusername"
password = "mypassword"
protocol = "https"
/>
Using Fiddler to inspect the process a bit further
<!--- do this for fiddler --->
proxyHost = "127.0.0.1"
proxyPort = "8888"
cfexchangeconnection appears to return the same response as if you attempted a connection via a browser to the Outlook Web Access page.
The issue may be that because the certificate is not a root authority cert that the dialog for accepting a non-root ca cert is being returned.
Environment:
SERVER1: SBS2003, Exchange
SERVER2: WIn2k, Coldfusion8, IIS, JRE6.0.14
both servers are on the same network (no firewall or whatever between them)
The SSL cert on SERVER1 is self signed
Question:
a) If it is the root authority dialog, how do we overcome this?
b) what else could it be? Fiddler appears to indicate that the certificate is correctly installed.
c) are there any specific configurations that need to be made to Exchange to make this work?
Help!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi srikanth,
Thanks for the reply, however the addition of the domain in front of the username didn't change the error message.
I tried forward and back slash ( DOMAIN/username and DOMAIN\username ) just in case
We have also purchased a "real" SSL cert just in case that was the issue -- waiting on it to come through so we can test that.
I don't suppose there's a way to get a more helpful error message out of the thing?
Business Accounts
Answer for Membership
by: srikanthmadishettiPosted on 2009-08-02 at 23:06:09ID: 25002141
just a quick comment ,Enter ur user name as
urdomain/username
Ex:
comp
where