LearnItFirst User Forum

Welcome Guest

Exchange Server Forums » Exchange Server » Mail Clients (Outlook/OWA/et al) » Exchange 2007 Webdav authentication using LTPA

Exchange 2007 Webdav authentication using LTPA

Options

Previous Topic · Next Topic

dilipinexchange

Posted: Wednesday, November 17, 2010 12:51:00 AM

Rank: Newbie

Joined: 11/9/2009
Posts: 2
Points: 6
Where do you live?: indore

We have Exchange 2007 and WPS 6.0 server which are protected by webseal and it provide SSO solution among them.
It means, portal users are able to logged-in portal server and the same user session is able to access Exchange server items.
When we logged in portal server, we received following cookies in browser,
(https://<webseal server fully qualified name>/wps/myportal/)

1) JSESSIONID
0000Bz1UdqcpoFca0vtYYwoK012:-1

2) PD-S-SESSION-ID
2_V9-g6fyyGSAauUJWAH53dsKoPccRTm5Hb132V0WYEC8Ak+bh

When we use OWA URL for access Exchange items, we received following cookies,

3) UserContext
f069a00a8f63408d861f7ee387bea305
The solution is working fine with web-access (in browser).

Now, we have to check the same thing with API (Exchange connector Webdav API) which connects with Exchange server and fetch the items from Exchange server. We prepared a web-application (includes exchange connector API) which deployed on WPS 6.0.
We are able to access web-application on portal. When we access Exchange URL, we create HTTPClient instance and GetMethod instance (including all cookies mentioned above with LTPA token) and pass the same URL which we have used through web-browser (mentioned above).
Our Exchange server gets connected and it returns status code 200. When we use the same connection for retrieving the inbox folder of Exchange server. It returns with 403 error.
We are in a stage of troubleshooting the things. we set cookies again when we retrieve the inbox folder but we received the same error.

Only thing which raise error for us is, when we create request for retrieving the inbox folder using LTPA token, JSESSIONID, PD-S-SESSION-ID and UserContext, it returns 403 error.

Note: Things are working fine when we connect with Exchange server using it's userid and password. In this case, Exchange server is not protected by webseal.

Please suggest us if you do have anything which is helpful for us.

Users browsing this topic

Guest

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.