AccessTokenCleanupTask | Community
Skip to main content
A
asultanuddin_me
November 15, 2018

AccessTokenCleanupTask

  • November 15, 2018
  • 3 replies
  • 2070 views

Does anyone know what is the reason for this error.

15.11.2018 03:07:23.000 *ERROR* [sling-default-199-Registered Service.1444] com.adobe.granite.oauth.server.impl.AccessTokenCleanupTask AccessTokenCleanupTask: General failure while trying to cleanup tokens

javax.jcr.LoginException: Cannot derive user name for bundle com.adobe.granite.oauth.server [149] and sub service null

        at org.apache.sling.jcr.base.AbstractSlingRepository2.loginService(AbstractSlingRepository2.java:311)

        at com.adobe.granite.oauth.server.impl.AccessTokenCleanupTask.cleanup(AccessTokenCleanupTask.java:116)

        at com.adobe.granite.oauth.server.impl.AccessTokenCleanupTask.run(AccessTokenCleanupTask.java:104)

        at org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:118)

        at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at java.lang.Thread.run(Thread.java:748)

TIA

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

smacdonald2008
smacdonald2008
November 15, 2018

What were you doing when you saw this issue?

A
asultanuddin_meAuthor
November 15, 2018

I do not even know what triggered this. This is running as a scheduler on its own. Could this be due to any permissions issue on a built-in system user?

S
Adobe Employee
sssfaffaaaAdobe Employee
Adobe Employee
November 16, 2018

Are you using oAuth in your system for login? If not, then you do not need to have this cleanup task enabled. To disable it go to HOST:PORT/system/console/components and find "com.adobe.granite.oauth.server.impl.AccessTokenCleanupTask" and stop it

A
asultanuddin_meAuthor
November 20, 2018

By default this component is active, so why it is giving an error in some environments and not others. Any idea?

A
asultanuddin_meAuthor
November 20, 2018

we are not using Oauth for login.

S
Adobe Employee
sssfaffaaaAdobe Employee
Adobe Employee
November 27, 2018

It seems that this server has a missing Service User Mapping that is affecting this task. You can either turn the component off, or you can compare the list of service user mappings in configMgr to the one in the server that doesn't have the issue and make sure any missing mapping is created on the faulty server

Terms & ConditionsAccessibility statement

Loading footer...