topic Re: 401 unauthorized webscript in Alfresco Archive

401 unauthorized webscript

robain — Thu, 11 Dec 2008 18:11:54 GMT

is it possible to capture this error in case of basic http authentication while accessing a webscript and give custom message.thanks

Re: 401 unauthorized webscript

mikeh — Thu, 11 Dec 2008 20:10:58 GMT

Please see: http://wiki.alfresco.com/wiki/Web_Scripts#Response_Status

Thanks,
Mike

Re: 401 unauthorized webscript

robain — Thu, 11 Dec 2008 20:22:37 GMT

Thanks Mike. But what we have there is a way to define our own flow to throw different http error exception. However 401 means you cannot even get to the point where the javascript code gets executed. Isnt that right? So how do I capture such exception.

Thanks

Re: 401 unauthorized webscript

mikeh — Thu, 11 Dec 2008 20:46:24 GMT

Good point - I've never tried the 401 case.

You could tell Tomcat to redirect instead via web.xml

<web-app>
  <error-page>
    <error-code>401</error-code>
    <location>/error401.jsp</location>
  </error-page>
…
<web-app>‍‍‍‍‍‍‍

Mike

Re: 401 unauthorized webscript

robain — Thu, 11 Dec 2008 20:53:52 GMT

Thanks Mike. That would solve the problem but this wont isolate the error messaging to the webscript alone but will be applied to any general 401 error. Was looking for something that could address this issue with webscripts only. Appreciate the post though. Thanks.

Re: 401 unauthorized webscript

t_broyer — Fri, 12 Dec 2008 09:34:57 GMT

You can place a 401.ftl at the root of the webscript search path (classes/alfresco/templates/webscripts or classes/alfresco/extension/templates/webscripts for instance).
In case the /401.ftl isn't found (which is the case by default), it defaults to /status.ftl

This will be used even for non-DeclarativeWebScripts (Java-backed web scripts for instance)

Re: 401 unauthorized webscript

robain — Fri, 12 Dec 2008 15:56:48 GMT

Thanks for the post boyer. But unfortunately it does not seem to work. The error I am getting right now is posted below. This is the tomcat message. Not sure if even the status.ftl is being used.

=============
HTTP Status 401 -

type Status report

message

description This request requires HTTP authentication ().
Apache Tomcat/5.5.23
==============

Mark,
Finally I also tried the web.xml configuration but seems like even that doesnt work for the alfresco webapp. It works for other web applications though. Any ideas?

Appreciate all the help guys.
Thanks

Re: 401 unauthorized webscript

t_broyer — Fri, 12 Dec 2008 16:19:48 GMT

D'oh, right!

It actually totally depends on the authenticator being used, as it has to send back the authentication challenge (WWW-Authenticate for HTTP auth, redirect to the login page for Web-Client auth (see below)).

So if you really want to control the 401 content, you'd be better writing your own org.alfresco.web.scripts.Authenticator and setting it up in the web.xml (either replacing the BasicHttpAuthenticator for /alfresco/s and /alfresco/service, or defining your own URI space).

For instance, I quite easily put in place something similar to this proposal in a new, distinct URI space (this would IMO be The Right Way™ to do the Web-Client authentication BTW).

As a side note, the WebScriptRuntime is broken wrt HTTP (at least in 2.2, I didn't check in 3.0) as it sends back 401s (without WWW-Authenticate!) instead of 403s in the following cases:

the web script requires authentication (either user or admin) but is called with ?guest=true

the web script requires admin privileges be the authenticated user isn't an admin

Re: 401 unauthorized webscript

robain — Fri, 12 Dec 2008 17:03:33 GMT

Thanks for clarifying. How about the tomcat custom error page solution. That shouldnt require rewiring the authenticator, right? But why is that not working for alfresco?

Thanks

Re: 401 unauthorized webscript

t_broyer — Mon, 15 Dec 2008 09:12:30 GMT

That's because Alfresco uses response.setStatus(). Error pages are only used when response.sendError() is called or in case of an exception. (see section SRV.9.9.2 of the Servlet Specification 2.4)

Re: 401 unauthorized webscript

sylvain_d — Mon, 23 Feb 2009 13:16:46 GMT

I'm using Alfresco and Share but my alfresco is running under an another port than 8080
In order to get Share working I edited a lot of file to change the 8080.

I can now use Share but I've got an 401 error after saving a wiki page while Alfresco is trying to generate the feeds.
If I try the URL given, I've got a prompt saying that the url require an authentication and that the site indicate "Alfresco"

Why is Alfresco asking "itself" or Share for a password ?
How can I solve that ?

My stack :


13:57:30,389 INFO  [org.alfresco.repo.activities.feed.FeedTaskProcessor] >>> Generated 4 activity feed entries for 1 activity posts
13:57:32,041 INFO  [org.alfresco.repo.activities.post.lookup.PostLookup] Update: 1 activity posts
13:57:47,047 INFO  [org.alfresco.repo.activities.feed.FeedTaskProcessor] >>> Generated 0 activity feed entries for 1 activity posts
13:57:47,047 ERROR [org.alfresco.repo.activities.feed.local.LocalFeedGridJob] java.io.IOException: Server returned HTTP response code: 401 for URL: http://localhost:18200/alfresco/service/api/activities/templates/org/alfresco/wiki/*?format=json
13:57:47,047 ERROR [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Exception during generation of feeds
java.lang.Exception: Server returned HTTP response code: 401 for URL: http://localhost:18200/alfresco/service/api/activities/templates/org/alfresco/wiki/*?format=json
        at org.alfresco.repo.activities.feed.local.LocalFeedGridJob.execute(LocalFeedGridJob.java:64)
        at org.alfresco.repo.activities.feed.local.LocalFeedGenerator.generate(LocalFeedGenerator.java:102)
        at org.alfresco.repo.activities.feed.AbstractFeedGenerator.execute(AbstractFeedGenerator.java:133)
        at org.alfresco.repo.activities.feed.FeedGeneratorJob.execute(FeedGeneratorJob.java:56)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
13:58:00,658 INFO  [org.alfresco.repo.activities.feed.FeedTaskProcessor] >>> Generated 4 activity feed entries for 1 activity posts
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: 401 unauthorized webscript

luisg — Wed, 15 Apr 2009 15:10:50 GMT

hello there…

I installed the alfresco 3 stable with success. I had no problems until now:
I just used share one time to create a new project, just for tests. After create that project I get the following error in alfresco.log

16:02:09,150 ERROR [org.alfresco.repo.activities.feed.local.LocalFeedGridJob] java.io.IOException: Server returned HTTP response code: 400 for URL: http://localhost:8080/alfresco/service/api/activities/templates/org/alfresco/links/*?format=json
16:02:09,152 ERROR [org.alfresco.repo.activities.feed.AbstractFeedGenerator] Exception during generation of feeds
java.lang.Exception: Server returned HTTP response code: 400 for URL: http://localhost:8080/alfresco/service/api/activities/templates/org/alfresco/links/*?format=json
   at org.alfresco.repo.activities.feed.local.LocalFeedGridJob.execute(LocalFeedGridJob.java:64)
   at org.alfresco.repo.activities.feed.local.LocalFeedGenerator.generate(LocalFeedGenerator.java:102)
   at org.alfresco.repo.activities.feed.AbstractFeedGenerator.execute(AbstractFeedGenerator.java:133)
   at org.alfresco.repo.activities.feed.FeedGeneratorJob.execute(FeedGeneratorJob.java:56)
   at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
   at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)

I my alfresco is not running in default port (8080), but in 8280. I think the problem is that I missed to modify a configuration file somewhere. But where?

I changed all the 8080 to 8280 in the configuration files in:
- <Alfresco_Directory>/tomcat/webapps/share/WEB-INF/classes/alfresco/
- <Alfresco_Directory>/tomcat/webapps/studio/WEB-INF/classes/alfresco/
- <Alfresco_Directory>/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/

Can you please tell me what file I miss to modify?

Help, Thanks

Luis

Re: 401 unauthorized webscript

t_broyer — Wed, 15 Apr 2009 15:25:17 GMT

Probably (certainly) the "repo.remote.endpoint.url" property in repository.properties (in the "alfresco" webapp)