You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* From a client API perspective, there is really no way to truely update an existing authorizable node. All of the properties are protected, and there is no
89
95
* known way to update them. What we do here is essentially remove the existing authorizable as denoted by the authorizableID, and recreate it.
@@ -96,7 +102,7 @@ class AuthorizableProtoNodeDecorator extends ProtoNodeDecorator {
//If no security manager is present, then we are in the clear; otherwise, we need to check certain permissions
127
136
if(!securityManager){
128
137
log.debug "No SecurityManager found on this JVM. Sync of Users/Groups can continue"
@@ -166,6 +175,18 @@ class AuthorizableProtoNodeDecorator extends ProtoNodeDecorator {
166
175
}
167
176
}
168
177
178
+
/**
179
+
* @return the system's security manager, or null if one is not present
180
+
*/
181
+
SecurityManagergetSecurityManager() {
182
+
returnSystem.getSecurityManager()
183
+
}
184
+
185
+
186
+
UserManagergetUserManager(finalSessionsession) {
187
+
returnAccessControlUtil.getUserManager(session)
188
+
}
189
+
169
190
170
191
/**
171
192
* Normally we would call org.apache.jackrabbit.oak.jcr.delegate.UserDelegator.changePassword(String password) to change a password (this is what is publicly available through the Jackrabbit API)
@@ -178,10 +199,10 @@ class AuthorizableProtoNodeDecorator extends ProtoNodeDecorator {
178
199
*
179
200
* @throws IllegalStateException if security permissions required to run this are not there. @{code checkSecurityPermissions()} should be called before calling this method
0 commit comments