To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=23786
User kso changed the following:
What |Old value |New value
================================================================================
Assigned to|kso |abi
--------------------------------------------------------------------------------
Status|STARTED |NEW
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Mon Dec 5 07:22:05 -0800
2005 -------
Andreas,
this one is tricky. The problem is that those web apps are implementing their
own login user interface. Upon first try to access the protected resource one
will be redirected to a login page and the return from the request is that login
page along with some error code. OOo never displays error documents. It just
interprets the request return code and displays an appropriate error message
box. Thus, the user has no chance to enter any login information.
The problem described here with the WebCT app goes even one step further. OOo
gets started from inside a browser. The browser might even know the login data,
because once obtained they are kept in a cookie. Currently there is no way to
hand over this cookie to OOo. Even worse, OOo's HTTP client has no cookie
support at all.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
