[jira] Updated: (SLING-718) I18n: JcrResourceBundleResolver should use loginAdministrative() by default for zero-conf

["Alexander Klimetschek (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Klimetschek updated SLING-718:
----------------------------------------

    Attachment: SLING-718.patch

Patch that changes the default behaviour and also adjusts the config descriptions in metatype.properties

> I18n: JcrResourceBundleResolver should use loginAdministrative() by default for zero-conf
> -----------------------------------------------------------------------------------------
>
>                 Key: SLING-718
>                 URL: https://issues.apache.org/jira/browse/SLING-718
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Alexander Klimetschek
>         Attachments: SLING-718.patch
>
>
> If you import or change sling:message nodes in the repository (which is typically done as admin in development), the i18n JcrResourceBundlerResolver might not see it if the change happens in a restricted path (eg. /libs/i18n, where /libs has restricted access), since he logs in as anonymous by default. One can set a different username/password as osgi config, but this requires configuration. For a zero-config approach, the default should use the handy slingRepository.loginAdministrative().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.