nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Why is repo store insecure?

kgeis

The authentication runas attribute only works on Web Scripts that are on the Java classpath. This is because RepoStore defines an isSecure() method that returns false. There are references on the forum to this being a choice because of "security issues." I can't imagine the security issues that come from declaring the repo store secure? It's not like end users are going to be authoring web scripts.

Can anyone enlighten me?

Find more posts tagged with

Comments

mrogers

If a script is loaded from the classpath then its more trusted than a script loaded from the repository. The problem is malicious users authoring web scripts to gain more rights than they should have.

afaust

Hello,

"It's not like end users are going to be authoring web scripts."

Well - for the vast majority (99+ %) of end users, this may be true. But nevertheless, allowing dynamically supplied scripts to be run requires that some control over what these scripts do is lost. A developer / admin that has set up a complex Alfresco application can't vouch for it, none of the dynamic scripts have to be reviewed or even tested to be uploaded into Alfresco. As an integral piece of business IT infrastructure, it is necessary for Alfresco to default on the side of caution and consider these scripts "not secure". And the kind of potential havoc you can cause by the access to the additional API exposed to "secure" scripts is nothing to be trivialized - you can basically circumvent a lot of the standard mechanisms that way if you are an experienced programmer.

Regards
Axel

kgeis

The problem, as I see it, is concern about malicious administrators. Also, there is no guarantee that classpath web scripts have been reviewed or tested before deployment either. I definitely agree that the default should be to assume that dynamic web scripts are not secure, but this is all contextual and depends on your business environment. In my case, we have a controlled environment, and the agility of dynamic web scripts outweighs security concerns. I overrode my RepoStore to convince Alfresco that it is secure. It would have been nice if I could have done this through configuration instead of code.

mrogers

Agreed.

I don't think there's an easy solution here but I agree that a config option rather than code changes is better.

if you want alfresco to be changed, please contribute your suggestion and patch file to JIRA along with any justification.