topic Re: Getting username of the user who executed a repository tier web script in Alfresco Archive

Getting username of the user who executed a repository tier web script

mando_alvarado_ — Tue, 05 Feb 2013 22:14:10 GMT

Title pretty much sums it up.I need to obtain the current user's username within a repo-tier webscript's javascript code. By "current user", i mean the authenticated user that triggered the execution of said script.I have tried to obtain this information using the now famous (to me anyway) root scop

Re: Getting username of the user who executed a repository tier web script

abarisone — Wed, 06 Feb 2013 08:30:47 GMT

Hi,
that sounds strange since

person.properties.userName‍

gives you the name of the currently authenticated user.
Is your web script configured to have

<authentication>user</authentication>‍

in its desc file?
You may also use the debugger to check the content of the parameter…

Regards,
Andrea

Re: Getting username of the user who executed a repository tier web script

mando_alvarado_ — Wed, 06 Feb 2013 19:57:26 GMT

Yes, the authentication type is set to "user" in the xml desc file.

Also, when trying to enable the debugger, i get the following error:

The Web Script /alfresco/service/api/javascript/debugger has responded with a status of 500 - Internal Error.

500 Description:    An error inside the HTTP server which prevented it from fulfilling the request.

Message:   01060011 Wrapped Exception (with status template): null

Exception:   org.springframework.extensions.webscripts.WebScriptException - 01060011 Wrapped Exception (with status template): null

org.springframework.extensions.webscripts.AbstractWebScript.createStatusException(AbstractWebScript.java:1067)

Server:   Community v4.2.0 (4480) schema 6,020
Time:   Feb 6, 2013 1:56:05 PM

Diagnostics:   Inspect Web Script (org/springframework/extensions/webscripts/jsdebugger.post)

I am hitting wall after wall here.

Re: Getting username of the user who executed a repository tier web script

lista — Tue, 12 Feb 2013 10:36:29 GMT

JavaScript debugger won't work on headless servers and if you're starting Alfresco as a service, at least in my experience. Do you fall in these categories?

I'm not sure I understand what you mean by repo-tier, can you explain that to me?

Re: Getting username of the user who executed a repository tier web script

mando_alvarado_ — Thu, 14 Feb 2013 21:02:23 GMT

By repo-tier webscripts, I mean webscripts that are in alfresco, not share. I.E they reside in the following path: /tomcat/webapps/alfresco/WEB-INF/clases/alfresco/templates/webscripts/. I don't know if that is the right way to call these webscripts, but I seem to have picked up the term "repo-tier" from all the online reading I have done.

As for your other question, I have no idea what a headless server is. I AM running it as a service though. I looked up a solution to this problem and found a forum thread where someone apparently found a way around this. His solution was creating a set of .bat files and starting up alfresco with those. Unfortunately, it didn't work for me.

Re: Getting username of the user who executed a repository tier web script

lista — Sun, 17 Feb 2013 22:39:10 GMT

That is strange, I never encountered root objects not being available in web script. You're on your own on that one.
I'm not sure as to why starting Alfresco through a .bat file does not work for you, do you get a concrete error? There's a setenv.bat file too, maybe it's setting environment variables to something that's not correct (had this issue once)?

Re: Getting username of the user who executed a repository tier web script

mando_alvarado_ — Fri, 03 May 2013 23:13:49 GMT

So, after a few months, I stumbled upon a solution to this. I have no idea why this works, or what is going on under the hood, and frankly I don't care anymore. This was a stupid problem to have.

The problem is that apparently you can't use <javascript><transaction>none</transaction></javascript> in your webscript desc file. If you do, you won't have access to certain root scope objects. I fixed it by using <javascript><transaction>required</transaction></javascript>.

I think this should be mentioned somewhere.