atmcaseteam
dokuwiki version : Release 2014-09-29b "Hrun"
Hi there,
We are using dokuwiki for years without any trouble in our company, and since our IT started to level up the security levels on desktops/laptops (with numbered rules I can't figure out... and a brand new Windows 7 based device) we are no more able to upload media from the dokuwiki Media Manager ("Sorry, you don't have enough rights to upload files."), while we still get the capability with older devices..
In fact a dokuwiki logged user, having some role (ACL) on a namespace, can or cannot upload media files according to the device he is using: with a older desktop, we have no problem to get the upload function; while with the brand new "protected desktop", we can't, despite we still have rights to modify pages...
I can't understand how the configuration of the client desktop can have an influence on the dokuwiki process on the server side...
If someone have a good idea of the process where Media Manager decides to grant upload rights or not, I am interested by his/her science.
Many thanks for any help
andi
You're right. The device should make no difference. What auth backend are you using?
atmcaseteam
I'm glad to see that my feelings were right :)
We are using basic authentication: 'authplain'
[EDIT] I forgot to precise that even the user 'admin' (superuser) has the same behaviour...
andi
Hmm. That's even weirder. The only explanation I see is that the AJAX request loading the upload panel in the media manager for some reason does not get the same cookies as everything else and thus is treated as an unauthenticated request. Maybe check the requests in Chrome's network monitor.
atmcaseteam
Well! Our IT does not allow Chrome explorer. We only get IE and Firefox .
I can try to deal that with a FF plugin (as Firebug). But even though, it's not as simpler as that, because even firefox configuration is locked (but I can find a way to deal).
This analysis requires spending some time; hence I shan't give you feed back very quickly...
Thanks for help, anyhow!
Be back later
andi
good luck, and maybe get one of your IT guys to debug together with you.
atmcaseteam
At last, we finally pinpointed our problem.
The DNS domain changed so often, that some guys are still using old-fashioned domain name.
It appears that our last generation of devices, some restriction has been setup that, in some sort, filtered transmitted data between server and client, when using the wrong domain name.
Maybe, this restriction filters cookies data (???)
At that moment, we did not get any explanations from our IT... :(
Problem solved...