nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I fix error with Application Link

Loi Le Quang_mo7n07

Hi Pro.

I has install JSM data center and Confluenec data center on aws cloud

I am facing an error in jira service management (JSM) when I am creating Application Link with Confluence

error detail: "We can't enable the incoming authentication because ITSM Knowledge Base is not reachable."

How can I fix error?

Thanks.

Accepted answers

All comments

BHUSHAN PATIL_fap6cn

Hi @Loi Le Quang ,

This can occur due to several reasons.

The application link between the Jira and Confluence applications is not configured with "Oauth (Impersonation)" (it is configured with "Oauth" without impersonation):
Make sure that the user who is trying to configure a knowledge base exists in the both i.e Confluence and Jira user base and must have admin permissions.
Check if there is a reverse proxy misconfiguration either on the Jira or Confluence side.

For More details please refer following troubleshooting guides:

if you feel my input help you please accept the answer.

Regards,
Bhushan

Loi Le Quang_mo7n07

Thanks Bhushan a lot. Let me try your advices.

BHUSHAN PATIL_fap6cn

Hi @Loi Le Quang ,

Try this

Network Configuration:
- Ensure that both Jira Service Management and Confluence are within the same Virtual Private Cloud (VPC) on AWS. If they are in different VPCs, you might encounter connectivity issues unless there's proper VPC peering or network configurations in place.
Security Groups:
- Confirm that the security groups associated with both instances allow the necessary communication between them. Check the inbound and outbound rules to ensure that the required ports (e.g., HTTP/HTTPS) are open for communication between Jira and Confluence.
Firewall and Network ACLs:
- Review the firewall settings and Network ACLs (Access Control Lists) on AWS. Ensure that there are no rules blocking the communication between Jira and Confluence.
Load Balancer Settings:
- If you are using a proxy or load balancer in front of Jira or Confluence, ensure that it's correctly configured to allow traffic between the two applications.
Application Link Configuration:
- When setting up the application link, double-check the configuration for accuracy. Ensure that the URL and authentication settings specified during the application link setup are correct.
Logs and Diagnostics:
- Check the logs of both Jira Service Management and Confluence for any specific errors or warnings related to the connectivity between the two applications. These logs might provide more detailed information about the issue.

If the issue persists, consider reaching out to Atlassian support for further assistance.

Regards,
Bhushan

Loi Le Quang_mo7n07

Hi @BHUSHAN PATIL

First of all, thank you very much for your supports.

We already tried to config with "Oauth" without impersonation, but the error still the

About the list items you mentioned:

Network Configuration:
- Both Jira Service Management and Confluence are within the same Virtual Private Cloud (VPC) on AWS.
Security Groups:
- Because they are at the same VPC, so there is no problem.
Firewall and Network ACLs:
- There is no rule blocking the communication.
Load Balancer Settings:
- The same load balancer and VPC
Application Link Configuration:
- When setting up the application link, double-check the configuration for accuracy. Ensure that the URL and authentication settings specified during the application link setup are correct => Double checked.
Logs and Diagnostics:
- Can use specify where is the log?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server