Re: [jira] [Commented] (SLING-3854) Add configuration option to restrict service user mapper to system users

2015-02-25 Thread Antonio Sanso
thanks a lot Marius,

I will proceed with the release so

regards

antonio

On Feb 24, 2015, at 7:20 PM, Marius Petria mpet...@adobe.com wrote:

 Hi Antonio,
 
 For SLING-4312 I am waiting for Felix’s answer as he raised some concerns 
 about the approach. Currently I have nothing in trunk as I reverted my 
 stuff due to a compilation error, so I think you can go ahead with the 
 release I can do another one once we are clear on SLING-4312.
 
 
 Marius
 
 
 
 On 2/24/15, 6:23 PM, Antonio Sanso asa...@adobe.com wrote:
 
 thanks Tomek,
 
 AFAIU we have also  https://issues.apache.org/jira/browse/SLING-4312 in 
 to the game.
 This approach is currently under discussion in the dev list.
 @Marius what is your take here.  Are we ready for a release?
 
 regards
 
 antonio
 
 On Feb 24, 2015, at 4:58 PM, Tomek Rękawek (JIRA) j...@apache.org wrote:
 
 
   [ 
 https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.
 plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335026#c
 omment-14335026 ] 
 
 Tomek Rękawek commented on SLING-3854:
 --
 
 Hello,
 I'm interested in releasing the JCR Resource 2.5.0, which depends on 
 the Service User Mapper 1.0.5-SNAPSHOT. I think the dependency is caused 
 by this resolved task. Do you think we can release the Service User 
 Mapper to remove the SNAPSHOT dependency from the JCR Resource?
 
 Add configuration option to restrict service user mapper to system 
 users
 
 
 
   Key: SLING-3854
   URL: https://issues.apache.org/jira/browse/SLING-3854
   Project: Sling
Issue Type: Improvement
Components: Service User Mapper
  Reporter: angela
  Assignee: Antonio Sanso
   Fix For: Service User Mapper 1.1.0, JCR Resource 2.5.0
 
   Attachments: SLING-3854-patch2.txt, SLING-3854.patch
 
 
 JCR-3802 introduces the concept of system users that distinct from 
 regular user accounts and never have a password set. the API extensions 
 include to following ability to discover if a given User is actually a 
 system user: {{User.isSystemUser}}.
 It would be good if the service user mapping had a configuration 
 option that would restrict the mapping to dedicated service users i.e. 
 to users which are defined to be system users in case sling is running 
 on a JCR repository that implements jackrabbit API.
 
 
 
 --
 This message was sent by Atlassian JIRA
 (v6.3.4#6332)
 



Re: [jira] [Commented] (SLING-3854) Add configuration option to restrict service user mapper to system users

2015-02-24 Thread Antonio Sanso
thanks Tomek,

AFAIU we have also  https://issues.apache.org/jira/browse/SLING-4312 in to the 
game.
This approach is currently under discussion in the dev list.
@Marius what is your take here.  Are we ready for a release?

regards

antonio

On Feb 24, 2015, at 4:58 PM, Tomek Rękawek (JIRA) j...@apache.org wrote:

 
[ 
 https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335026#comment-14335026
  ] 
 
 Tomek Rękawek commented on SLING-3854:
 --
 
 Hello,
 I'm interested in releasing the JCR Resource 2.5.0, which depends on the 
 Service User Mapper 1.0.5-SNAPSHOT. I think the dependency is caused by this 
 resolved task. Do you think we can release the Service User Mapper to remove 
 the SNAPSHOT dependency from the JCR Resource?
 
 Add configuration option to restrict service user mapper to system users
 
 
Key: SLING-3854
URL: https://issues.apache.org/jira/browse/SLING-3854
Project: Sling
 Issue Type: Improvement
 Components: Service User Mapper
   Reporter: angela
   Assignee: Antonio Sanso
Fix For: Service User Mapper 1.1.0, JCR Resource 2.5.0
 
Attachments: SLING-3854-patch2.txt, SLING-3854.patch
 
 
 JCR-3802 introduces the concept of system users that distinct from regular 
 user accounts and never have a password set. the API extensions include to 
 following ability to discover if a given User is actually a system user: 
 {{User.isSystemUser}}.
 It would be good if the service user mapping had a configuration option that 
 would restrict the mapping to dedicated service users i.e. to users which 
 are defined to be system users in case sling is running on a JCR repository 
 that implements jackrabbit API.
 
 
 
 --
 This message was sent by Atlassian JIRA
 (v6.3.4#6332)



Re: [jira] [Commented] (SLING-3854) Add configuration option to restrict service user mapper to system users

2015-02-24 Thread Marius Petria
Hi Antonio,

For SLING-4312 I am waiting for Felix’s answer as he raised some concerns 
about the approach. Currently I have nothing in trunk as I reverted my 
stuff due to a compilation error, so I think you can go ahead with the 
release I can do another one once we are clear on SLING-4312.


Marius



On 2/24/15, 6:23 PM, Antonio Sanso asa...@adobe.com wrote:

thanks Tomek,

AFAIU we have also  https://issues.apache.org/jira/browse/SLING-4312 in 
to the game.
This approach is currently under discussion in the dev list.
@Marius what is your take here.  Are we ready for a release?

regards

antonio

On Feb 24, 2015, at 4:58 PM, Tomek Rękawek (JIRA) j...@apache.org wrote:

 
[ 
https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.
plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335026#c
omment-14335026 ] 
 
 Tomek Rękawek commented on SLING-3854:
 --
 
 Hello,
 I'm interested in releasing the JCR Resource 2.5.0, which depends on 
the Service User Mapper 1.0.5-SNAPSHOT. I think the dependency is caused 
by this resolved task. Do you think we can release the Service User 
Mapper to remove the SNAPSHOT dependency from the JCR Resource?
 
 Add configuration option to restrict service user mapper to system 
users
 

 
Key: SLING-3854
URL: https://issues.apache.org/jira/browse/SLING-3854
Project: Sling
 Issue Type: Improvement
 Components: Service User Mapper
   Reporter: angela
   Assignee: Antonio Sanso
Fix For: Service User Mapper 1.1.0, JCR Resource 2.5.0
 
Attachments: SLING-3854-patch2.txt, SLING-3854.patch
 
 
 JCR-3802 introduces the concept of system users that distinct from 
regular user accounts and never have a password set. the API extensions 
include to following ability to discover if a given User is actually a 
system user: {{User.isSystemUser}}.
 It would be good if the service user mapping had a configuration 
option that would restrict the mapping to dedicated service users i.e. 
to users which are defined to be system users in case sling is running 
on a JCR repository that implements jackrabbit API.
 
 
 
 --
 This message was sent by Atlassian JIRA
 (v6.3.4#6332)