Sorry, my title got a bit mangled.  I'm specifically asking about accessing keystore services in a custom java application.  Neither of those links are applicable.

We have an AEM service that needs to integrate with an azure keystore.  The Azure java libraries aren't OSGI packages and I haven't been able to get them to work wrapping them myself, likely because their dependency tree is just huge.  Anyone else been down this road before and can they offer any ad...

Does AEM provide an actual implementation of the TaskManager API out of the box?  All I can see is the interface.  Anyway our answer ended up being to just write a servlet to change a task's status.

I'm creating an inbox replacement to deal with the massive number of asyncrollout messages we get.  Unfortunately the url the existing inbox uses,. /libs/granite/taskmanager/updatetask , looks like it's restricted to what can call it and throws a 403 Forbidden when called outside of the AEM inboxes....

We recently updated to the 6.5.10 uberjar and started receiving excessively long build logs.  It looks like the unit tests have been set to debug log level and we're getting repeated messages from org.apache.sling.testing.mock.sling.MockAdapterManagerImpl whenever it mocks a sling service.  We haven...

In case anyone else is looking for this, the admin user can see all jobs, but not just anyone in group administrators.  

I'm on AEM 6.5.7 If I  bring up the Async Jobs Status page I can see the jobs I started, but not jobs other users have started.  Is there anyway to see everything?

We usually set up the translation project first and then add pages to it. The first time we do that it works fine. Sometimes though, around 20% of the time, when we add a newly created page to the language copy we see this behavior. This is also only an issue when we update a language copy. So in yo...

If we have a page like /content/site/en/foo and we create a language copy like /content/site/pt/foo. We translate that language copy and everything is great.  Sometimes though when we look to add a sub page, say /content/site/en/foo/bar, instead of adding creating it at /content/site/pt/foo/bar like...

Thanks, but adding the rights didn't address the issue. I'm also working on the page as a member of the administrators group, so permissions to see users shouldn't be the issue.