You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/12/12 09:11:00 UTC

[jira] [Resolved] (SLING-8171) Adjust https://sling.apache.org/documentation/the-sling-engine/service-authentication.html#service-user-mappings to reflect the principal based mapping

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

Konrad Windszus resolved SLING-8171.
------------------------------------
    Resolution: Fixed

Updated documentation in https://github.com/apache/sling-site/commit/4db71dd9b92d7c56aaebddee26202974dc4e86d5.
Published updated site with https://github.com/apache/sling-site/commit/c97404380b7aa82c93d1df35b2e0871cf00831b1.

> Adjust https://sling.apache.org/documentation/the-sling-engine/service-authentication.html#service-user-mappings to reflect the principal based mapping
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-8171
>                 URL: https://issues.apache.org/jira/browse/SLING-8171
>             Project: Sling
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>
> The change being introduced by SLING-6963 should be reflected in https://sling.apache.org/documentation/the-sling-engine/service-authentication.html#service-user-mappings.
> Also it should clearly indicate how to differentiate between principals and jcr user ids.
> Also the implications like the one outlined in OAK-7952 should be clearly mentioned there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)