Confluence is not able to communicate with JIRA for authentication after domain change
Asked by Akhilesh Gupta:

We had to change the JIRA application URL because there was a change in domain, for example if old URL was oldURL.company:8180 then we did it to newURL.company:8180, The new URL for JIRA is working perfectly fine.

But when we try to login into confluence, there is an authentication error. From the log we found out that confluence is still using the old JIRA url for authentication, question is how to update this URL at confluence so that it can connect to correct JIRA application.

I also looked into to see connected application in JIRA under Administration \> Applications \> Application links, and there Confluence is listed with status Connected, Kindly let me know how can I change the URL of JIRA on confluence side.

Below is log of confluence for more information:

```
2017-04-13 11:18:58,060 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 327681 ] was not successful, attempting FULL2017-04-13 11:18:58,482 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache failed synchronisation complete for directory [ 327681 ] in [ 422ms ]2017-04-13 11:18:58,497 ERROR [Caesium-1-4] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 327681 ].com.atlassian.crowd.exception.OperationFailedException: java.net.UnknownHostException: inggnm7coa.ww007.siemens.netat com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:493)at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:557)at com.atlassian.crowd.directory.RemoteCrowdDirectory.searchUsers(RemoteCrowdDirectory.java:371)at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.findAllRemoteUsers(RemoteDirectoryCacheRefresher.java:55)at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.synchroniseAllUsers(RemoteDirectoryCacheRefresher.java:90)at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:89)at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseAll(EventTokenChangedCacheRefresher.java:67)at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:1122)at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:76)at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50)at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobRunner.runJob(DirectoryPollerJobRunner.java:93)at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.doRunJob(JobRunnerWrapper.java:129)at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.lambda$runJob$0(JobRunnerWrapper.java:89)at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:82)at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:72)at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.runJob(JobRunnerWrapper.java:89)at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:401)at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:396)at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:349)at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:255)at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:252)at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)at java.lang.Thread.run(Unknown Source)Caused by: java.net.UnknownHostException: inggnm7coa.ww007.siemens.netat java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)at java.net.InetAddress.getAddressesFromNameService(Unknown Source)at java.net.InetAddress.getAllByName0(Unknown Source)at java.net.InetAddress.getAllByName(Unknown Source)at java.net.InetAddress.getAllByName(Unknown Source)at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:111)at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)at org.apache.http.impl.client.cache.CachingExec.callBackend(CachingExec.java:592)at org.apache.http.impl.client.cache.CachingExec.execute(CachingExec.java:269)at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.executeCrowdServiceMethod(RestExecutor.java:598)at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:481)... 27 more
```


Answers:
author: Jobin Kuruvilla [Adaptavist]
body: Check under **Administration** \> **General Configuration** \> **User Directories**.

See <https://confluence.atlassian.com/doc/connecting-to-crowd-or-jira-for-user-management-229838465.html#ConnectingtoCrowdorJIRAforUserManagement-ConnectingConfluencetoJIRAapplicationsforUserManagement> for more details.

comments: author: Akhilesh Gupta
body: HI Thanks for reply But this links describes the initial steps to configure the connection between JIRA and confluence. What my problem is I have already done these steps and after running fine for some time the URL of JIRA is changed , and I need to change the URL of JIRA the confluence tries to connect.

Further I am not able to login confluence to chnage anything at confluence side


author: Jobin Kuruvilla [Adaptavist]
body: I am guessing you configured those links and user directories using the old links. That explains why you are unable to login.

Do you have a local admin user in Confluence? If so, login using that user and update the application links and user directory configuration using the new url.

If you do not have a local admin user, create one as explained here: [https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html](https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html?)


Tags: authentication

user-management