[
https://issues.jenkins-ci.org/browse/JENKINS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159315#comment-159315
]
Lars Vonk commented on JENKINS-9740:
------------------------------------
any updates or workaround? same goes for the openid which is unusable then
disabling anonymous access.
> Access to static content is denied when jenkins works in private mode
> (anonymous access is disabled)
> ----------------------------------------------------------------------------------------------------
>
> Key: JENKINS-9740
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9740
> Project: Jenkins
> Issue Type: Bug
> Components: core, security
> Reporter: jsirex
>
> When jenkins works in private mode (anonymous access is disabled) I unable to
> access some static content. It affects to some things like:
> * Adding slaves via Web Start (Jnlp) -> install as service
> {quote}jenkins slave tries access thorugh url jenkins-slave.jnlp which is
> unaccessible with out authorization
> I have to manually download this file and update xml-config with new
> path{quote}
> * Email notification contains links to static images which also unavailable
> for anonymous
> * Jira-plugin leave comments with links to static images too
> * etc
> I think an permission "Allow access to static content
> (${JENKINS_URL}/static/*)" which I can assign to anonymous will fix many such
> problems
> PS. Not sure what component I have to specify
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
