documents authentication issue since upgrade to 5.0.11

[twickle]

Hello, we have upgraded our server to 5.0.11 NE two days ago.

since we did that, we have the following issue:

-a user has a special logon domain and logs on via https://customer.zimbradomain.tld
-the host name is zimbra.zimbradomain.tld

-if the user switches to documents tab and clicks on a notebook, he will be forwarded to the notebook unter the url https://zimbra.zimbradomain.tld/.... and not unter customer.zimbradomain.tld.
-therefore the user gets a logon popup of course

Is there a patch to correct the document links again?

Thanks,
Thomas

[Klug]

What is the mail domain for this customer ?

If the mail domain for the customer is used by this customer only, you should setup zimbraPublicServiceHostname "correctly" for this domain.

[SOLVED] "Public service host name" in domain creation

[twickle]

Hello Klug,

thanks, that fixes the URLs but destroys the document standard layout.
Now within that changed domain all styles in the document listing is gone.

Thanks,
Thomas

[Klug]

Which "style in the documents listing" ?
Could you post a couple of screenshots (what you're getting and what you'd like to get) ?

[twickle]

Hi,

ok.. that is what i get after i have settled the zimbraPublicServiceHostname for a domain, documents get listed like that:


PicPaste - documents.jpg

what i want is the "classic" standard layout:


PicPaste - documents2.jpg

i guess this is also only a setting issue.

thanks,
Thomas

[Klug]

I guess you correctly restarted mailboxd after changing the parameter ?

You might be hitting this bug : Bug 25504 – wiki.css URL should use host AND PORT in location header

Can you try to access the wiki.css through https://customer.zimbradomain.tld/zimbra/css/wiki.css ?

[twickle]

hm it is solved. Thanks.

The problem was that the URL to the stylesheet was http and the server mode was https only.

so a zmprov md domain.tld zimbraPublicServiceProtocol https did the trick.

Thanks again,
Thomas

[twickle]

Hello,

the problem is solved for *OWN* documents and shared documents of users, which are inside the SAME domain.

But imagine this constellation:

-User 1 (user1@sd1.domain.tld) -> LoginURL & Public Service URL: https://sd1.domain.tld
-User 2 (user2@sd2.domain.tld) ->
https://sd2.domain.tld
(both on the same zimbra server of course)

User 1 has a notebook called test, which is shared to User 2.
If User 2 goes to his documents tab, he gets own notebooks having the "right" (his) public service URL, but the shared document folder of User1 is containing the public service name of user 1 - with the effect, that he gets again an authentication popup when accessing that shared notebook.

https://sd1.domain.tld/home/user1@sd1.domain.tld/test

instead of

https://sd2.domain.tld/home/user1@sd1.domain.tld/test

any idea for fixing that?

Thanks,
Thomas