It appears that the LoginException was because I was mistakenly invoking the resolver factory getServiceResourceResolver() method instead of using getResourceResolver() with the request authInfo.
With this change I now don't see a LoginException, but I get a JCR AccessDeniedException when the thread tries to perform the first write. Is this approach feasible, and I just need to see if there's an issue with users or permissions? From: John Logan On Friday, March 17, 2017 8:39 AM, John Logan wrote: > I tried using ResourceResolverFactory.getResourceResolver() > along with the AuthenticationInfo object from the request > attributes, and this yielded a LoginException.
