Issue 107765 - WebDav support - autentication problem
Summary: WebDav support - autentication problem
Status: ACCEPTED
Alias: None
Product: ucb
Classification: Code
Component: code (show other issues)
Version: OOO310m19
Hardware: All All
: P3 Trivial (vote)
Target Milestone: 3.x
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-18 10:00 UTC by paolomantovani
Modified: 2013-01-29 21:42 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description paolomantovani 2009-12-18 10:00:25 UTC 
scenario:

we have a server running "Oracle Content Service" as document management system.
http://www.oracle.com/technology/products/ocontentservices/index.html

Documents are made accessible as webdav resources.

In order to access documents, the first step for a client (e.g. OpenOffice.org)
is to authenticate with the Oracle Content Services instance.
To connect to an instance, you will need a URL and port, as well as a valid
username and password.

Openoffice seems unable to perform the autentication in order to open documents.

Please consider the following StarBasic demo code:

sUrl = "http://oraclecollaboration.blabla.dom:7777/content/dav/test.doc"
Dim mArgs(0) As New com.sun.star.beans.PropertyValue
mArgs(0).Name = "InteractionHandler"
mArgs(0).Value = CreateUnoService("com.sun.star.task.InteractionHandler")
oDoc = StarDesktop.loadComponentFromUrl(sUrl, "_default", 0, mArgs())


As expected, the InteractionHandler service shows the autentication dialog, but
even providing valid username and password Openoffice is not able to autenticate
with the server.

This seems depending from the fact that Oracle Content Services uses a Remote
Login Manager server in order to autenticate sessions.

more documentation here:

http://download.oracle.com/docs/cd/B25553_01/content.1012/b25277/connecting.htm#sthref10
Comment 1 tkr 2009-12-18 11:11:30 UTC 
The reason why the authentication failed is that OOo doesn't support HTTP
cookies yet.

Taking over and CC kso.
Comment 2 tkr 2010-01-06 08:47:29 UTC 
@paolomantovani: 

Is it possible to get more additional information about the network
communication between OOo and server?

I need the response header of the HTTP request while accessing the webdav resource.
Comment 3 tkr 2010-02-08 08:55:26 UTC 
No time to fix this for OOo 3.3