Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sorry, a communication error occurred while trying to contact the remote authentication server


Hi everyone

We unsuddenly have the following error when trying to login to JIRA (Jira Server 7.3.1 ):

Sorry, a communication error occurred while trying to contact the remote authentication server.

Although crowd works well. Authorization in Confluence works. And we can't authorize to JIRA as local user too. We tried to reboot JIRA few times. Nothing changed.


2021-01-20 09:59:01,079 JIRA-Bootstrap ERROR [c.a.s.core.lifecycle.DefaultLifecycleManager] LifecycleAware.onStart() failed for component with class 'com.atlassian.oauth.serviceprovider.internal.ExpiredSessionRemoverScheduler' from
plugin 'com.atlassian.oauth.serviceprovider'
java.lang.IllegalArgumentException: Job handler already registered: Service Provider Session Remover
at com.atlassian.scheduler.compat.clustered.ClusteredCompatibilityPluginScheduler.registerJobHandler(
at com.atlassian.scheduler.compat.AutoDetectingCompatibilityPluginScheduler.registerJobHandler(
at com.atlassian.oauth.serviceprovider.internal.ExpiredSessionRemoverScheduler.onStart(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$4.consume(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$4.consume(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecyleAware(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyOnStartIfStartedAndEnabled(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.access$300(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$3.evaluate(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$3.evaluate(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecycleAwares(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyStartableLifecycleAwares(
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.onPluginEnabled(
... 2 filtered
at java.lang.reflect.Method.invoke(
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(
at com.atlassian.event.internal.EventPublisherImpl.publish(
at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(
at com.atlassian.plugin.manager.DefaultPluginManager.broadcastIgnoreError(
at com.atlassian.plugin.manager.DefaultPluginManager.onPluginRefresh(
... 3 filtered
at java.lang.reflect.Method.invoke(

Please help us in resolving this.

1 answer

0 votes

Hi @N,

Unfortunately, the error that you have provided has nothing to do with the user authentication mechanism in Jira.

You should retrieve your local Jira Admin user account first and then troubleshoot the problem with the connection to the Crowd server. You may refer to Retrieving the JIRA Administrator.

I hope that this helps.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events