Issue 1: Can now use forms or basic authentication with OWA
Status:  Fixed
Owner:
Closed:  May 2007
Cc:
Reported by Dave.Gud...@gmail.com, Feb 8, 2007
When installed in a development / testing environment the onebox module
works, however when moved to a live environment the same code will not work.

Both environments are Win 2003, running .Net 2 on IIS 6. Differences
between the environments:

test:
Single server which acts as domain controller, Exchange server and IIS server.

live:
clustered exchange servers
multiple Active directory domains and domain controllers.


When viewing the service directly in a browser on the test server you get
the expected xml output:

--

<OneBoxResults>
<title>
<urlText>My Company Employee Directory Results</urlText>
<urlLink>
http://mywebserver/DirWebSvc/DirectoryService.asmx/GoogleUsers?query=gudgeon
</urlLink>
</title>
<IMAGE_SOURCE>
http://mywebserver/Path/toThis/Project/employee.bmp
</IMAGE_SOURCE>
<MODULE_RESULT>
<Title>John Smith</Title>
<Field name="firstname">John</Field>
<Field name="lastname">Smith</Field>
<Field name="email">user@domain</Field>
<Field name="0800_0815">Free</Field>
<Field name="0815_0830">Free</Field>
<Field name="0830_0845">Free</Field>

...

--


In the live environment we get xml but no user details are returned

--

<OneBoxResults>
 <title>
  <urlText>My Company Employee Directory Results</urlText> 
 
<urlLink>http://mywebserver/DirWebSvc/DirectoryService.asmx/GoogleUsers?query=smith</urlLink>

  </title>
 
<IMAGE_SOURCE>http://mywebserver/Path/toThis/Project/employee.bmp</IMAGE_SOURCE>

</OneBoxResults>

--

additional information:


I have altered all of the configuration details (ldap path, username,
password, etc) to incorrect values to check that those used are correct.
When incorrect I will always receive an error message rather than the empty
xml shown above.

Having looked through the code it would seem that the query to the LDAP
server is not returning any results. Why would this be the case? The
username and password supplied is definitely valid (altering the password
results in an authorization error) and I have used the same login details
to query the LDAP server elsewhere in another app in the live environment
so I know that they will do the job.

Any help would be much appreciated.

Many thanks

Dave
Apr 18, 2007
#1 gary.com...@gmail.com
I'm working on a code fix that will allow Exchange 2003 users who are using forms 
based authentication to login and get the free/busy schedule.  Also the code assumes 
every LDAP user has an email address in exchange so I'll add a quick check first.. 
this will allow those uses to still display their LDAP info.

Gary
Status: Started
Owner: gary.comstock
Cc: jeff.ragusa
May 7, 2007
#2 gary.com...@gmail.com
Created and authentication class file with option now for OWA basic or forms 
authentication and moved all configuration to the web.config file.  Also code no 
longer assumes all LDAP users had an email account.
Summary: Can now use forms or basic authentication with OWA
Status: Fixed