I solved the SSO error in catalina.out. This was the result of an apache misconfiguration. ("Limit GET POST" instead of "limit GET") I'm now back to the trouble with the Tree view. It still looks that authorization headers are missing in some requests. Does anybody know if this is a correct assumption? And if it is, how can I solve this? -----Oorspronkelijk bericht----- Van: [email protected] [mailto:[email protected]] Namens Mark Jas Verzonden: donderdag 14 maart 2013 13:43 Aan: XWiki Users Onderwerp: Re: [xwiki-users] TRANSPORT_ERROR with SSO in tree view Hi Marius, There are a lot of AJAX requests, some work, some don't. All requests have cookie headers. But it looks like the failed requests have no authorization header, and the other requests do have one. On the main page I see some failed requests (without authorization header) and right after, the same request again with authorization header that succeeds! Looks like some kind of retry. With the REST request, I do not see this duplicate requests. Mark -----Oorspronkelijk bericht----- Van: [email protected] [mailto:[email protected]] Namens Marius Dumitru Florea Verzonden: donderdag 14 maart 2013 12:52 Aan: XWiki Users Onderwerp: Re: [xwiki-users] TRANSPORT_ERROR with SSO in tree view Ok, so the problem is: * either the AJAX requests don't have the necessary authentication information * or the REST system doesn't understand or doesn't handle properly the authentication information from the request. All AJAX requests should have all the cookies that the main request (for the edit mode) has. So if the authentication information is stored in cookies then it is send with the AJAX requests. The first thing to check is if the AJAX requests (logged in the Firebug console) have the authentication information. I don't know how the Kerberos SSO works nor if it integrates well with REST. We need the help of a REST guru here :) Thanks, Marius On Thu, Mar 14, 2013 at 1:37 PM, Mark Jas <[email protected]> wrote:

Forgot to mention: Catalina.out shows me this:

2013-03-14 12:35:58,430 [http://xwiki/xwiki/bin/get/Main/WebHome?xpage=xpart&vm=commentsinline.vm] WARN a.t.TrustedLDAPAuthServiceImpl - Failed to resolve remote user. It usually mean that no SSO information has been provided to XWiki.

-----Oorspronkelijk bericht----- Van: [email protected] [mailto:[email protected]] Namens Mark Jas Verzonden: donderdag 14 maart 2013 12:34 Aan: XWiki Users Onderwerp: Re: [xwiki-users] TRANSPORT_ERROR with SSO in tree view

Hi Marius,

I used firebug like you said. Here my findings: - Scheme is ok. (all http) - hostname is ok (all "xwiki") - the console shows me a lot of request with a "401 authorization required" (not only on the tree page, but also on other pages) - all the REST request on the tree page have "401 authorization required" responses. - No authentication errors in apache logs - http://xwiki/xwiki/rest/ with SSO gives me an "Internal Server Error" (no error in apache logs) - http://xwiki/xwiki/rest/ without SSO gives me some XML - All REST requests I see in the console are the same: http://xwiki/xwiki/rest/wikis/xwiki/spaces?r=221031

Hope you can help. Thanks. Mark

-----Oorspronkelijk bericht----- Van: [email protected] [mailto:[email protected]] Namens Marius Dumitru Florea Verzonden: donderdag 14 maart 2013 8:22 Aan: XWiki Users Onderwerp: Re: [xwiki-users] TRANSPORT_ERROR with SSO in tree view

On Wed, Mar 13, 2013 at 9:06 PM, Mark Jas <[email protected]> wrote:

...

Hello,

I get a popup with the error “Server returned TRANSPORT_ERROR with no error message.” If I select the tree view in the document index.

I’m using xwiki 4.5 with kerberos SSO. If I disable kerberos in apache and use the normal login, everything works just fine.

Is this a bug?

Could be. TRANSPORT_ERROR normally happens when a request made by the tree fails (usually because the URL is bad). The tree uses the REST system to fetch its data, so all requests made by the tree are /rest/ requests. It would be of great help if you could tell us what requests are failing (their URL is important). In order to check this you can use Firefox with its Firebug extension. This extension has a Console tab where you can see all the (AJAX) requests made by the editor and its tree, if the console was opened before the page was loaded, otherwise you need to reload the page. The failed requests are displayed in red so they are easy to notice. You can click on each request to get more information, but more importantly you can right click to get the full URL with parameters. Post here the bad URLs and also the URL for the edit mode.

The things to check are: * are the REST URLs using the same scheme (HTTP/HTTPS) as the edit mode URL? * do they have the same domain? * is the REST system working when Kerberos SSO is enabled?

Thanks, Marius

...

Mark

_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users

_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users

_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users

_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users

users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users