FlexNet Code Insight ScriptRunner returns "Current user admin doesn't have script admin role" error

[#1]

Summary

This article provides a resolution for the error: Current user admin doesn't have script admin role, please contact your System Administrator.

Symptoms

While running a scriptRunner script in FlexNet Code Insight 6.8 or later with a user with script admin role, you receive the following error:

    Current user admin doesn't have script admin role, please contact your Palamida System Administrator

Resolution

Try the following steps:

1. Try deleting the $USER/.palamida/config/scriptRunner/scriptRunner.properties file to get rid of cached scriptRunner credentials.

NOTE: The location of this file will depend on whether or not you are running scriptRunner from the server or client machines.

Then make sure that you are able to open the Groovy console using only the scriptRunner username:

./scriptRunner.sh -u admin

And enter the JWT token for admin when prompted.

If you can get to the groovy console, you?ve authenticated, and you know scriptRunner itself is not the problem.

2. Ensure that any URLs passed to scriptRunner are formatted correctly. For example:

-server flag no longer takes just hostname, but full URL like http://servername:8888/palamida/

Conversely, the -scan_server flag now takes just servername:8888

3. Ensure that the -c flag provides the core server location followed by a "/". For example:

http://<CORESERVER_URL>:8888/palamida/

Note that the trailing slash is necessary.

4. Check $palamida/scriptRunner/log/scriptRunner.log for any additional stacktrace/exception.

[dgstangel]

The same error "Current user admin doesn't have script admin role" was also returned when our client system's Java trust store did not trust the SSL certificate presented by the core server.  But the message came even before a connection to the server was established

[ajinkyab]

Hi @dgstangel ,  I am also getting the same error. How did you resolve it?

Thanks,
Ajinkya 

[ajinkyab]

Issue was with the java version. When I pointed to correct java version, it worked.