Hi Ingo,
thanks for helping!
This indeed eliminates the null pointer. But the real problem is there
is nothing stored in usersPath and it is thus . Also, when you do not
authorize, your userId will be .
In LockImpl.computeSubjectUriFromPrincipal
the statement
There seems to be a bug in NamespaceConfig.getUsersPath(). It returns
null in initialization:
Thread [main] (Suspended (breakpoint at line 860 in SecurityImpl))
SecurityImplAllGrant(SecurityImpl).getPrincipal(SlideToken) line: 860
SecurityImplAllGrant(SecurityImpl).hasPermission(SlideToken,
Just a guess: Should the relevant part of the diff not looke like
this?
public String getUsersPath() {
-return usersPath;
+// TODO: get rid of user_collection parameter
+if (resolvedUsersPath == null) {
+if (usersPath == null ||
