cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to delete or disable user through share. - SOLVED

bens
Champ in-the-making
Champ in-the-making
Hi all.

I'm unable to delete or disable users in Alfresco Community 4.2.0 via the share interface.  I'm moderately technical but am completely stumped and am hoping that someone can help point me in the right direction.

Our environment is as follows:
Windows Server 2008. IIS 7.5
Tomcat with ISAPI redirector running the Alfresco webapps.
Anonymous authentication

If I try to disable a user, here's some example headings that come through:

https://mywebsite.com/share/proxy/alfresco/api/people/testuser

PUT /share/proxy/alfresco/api/people/testuser HTTP/1.1
Host: mywebsite.com
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en,en-gb;q=0.7,fr-ca;q=0.3
Accept-Encoding: gzip, deflate
X-Requested-With: application/json
Content-Type: application/json; charset=UTF-8
Referer: https://mywebsite.com/share/page/console/admin-console/users
Content-Length: 135
Cookie: JSESSIONID=SOMEVALUES; alfLogin=123456789; alfUsername3=myusername; AJS.conglomerate.cookie=""
Authorization: Basic YnNoYXBpcm86MzE0MTU5cGkh
Connection: keep-alive
{"firstName":"test","lastName":"user","email":"someemail@mywebsite.com","disableAccount":true,"quota":-1,"addGroups":[],"removeGroups":[]}

HTTP/1.1 401 Unauthorized
Content-Type: text/html
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 08 May 2014 20:22:35 GMT
Content-Length: 1293



It seems that whenever a PUT or DELETE directive comes through, it returns an unauthorized from the webserver.  I tried implementing basic authentication and connected as an authenticated user but still received a 401.

Does anyone have any experience with this issue and can help me troubleshoot?  I'm certain it's going to be one of those "change this one line" solutions.

Many thanks,
Ben
6 REPLIES 6

romschn
Star Collaborator
Star Collaborator
You mentioned you have implemented basic authentication. Can you try without that and see if it works? I mean out-of-the-box without your basic authentication implementation is it working or not?

bens
Champ in-the-making
Champ in-the-making
Thanks Ramesh.
It was initially set up with only anonymous access just due to the variety of users accessing the system.  In an effort to troubleshoot this, I read that IIS 7.5 needs minimally Basic Authentication to allow WebDAV PUTs and DELETEs.
As such, I then implemented Basic Authentication on the site to test, but even then I received 401 Unaithorized responses.

romschn
Star Collaborator
Star Collaborator
I have not tried this but can you please check the "Providers" under "Windows Authentication" and if NTLM is not on the top in negotiate then have it at the top and see if it works for you or not.
Hope this helps.

bens
Champ in-the-making
Champ in-the-making
OK, removed "Negotiate" so only NTLM was at the top.  Applied and restarted the webserver.  Attempting to delete or disable a user realized the same error.

If I enable Basic Authentication now however, I now get a 403 Forbidden error and the page fails submission.

Thanks for your help.  I'm stumped with this.

romschn
Star Collaborator
Star Collaborator
Okay, I am not very much sure if this will help solve the problem or not. However, Can you please try enabling the forms authentication and see if PUT request works or not?

Hope this helps.

bens
Champ in-the-making
Champ in-the-making
Thanks for all of your help.  I solved the problem.  It turns out that I hadn't disabled the WebDAV module in IIS, so it was blocking the DELETE directives, etc. that were meant for Tomcat.  With the WebDAV module disabled, everything is working fine.

Best regards!
Ben