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; } } }

Deploy Companion App w/Trusted Domain

James Fenton

Hi,

I've seen that this question has been asked a few times, but I haven't seen a viable solution. I'm in the process of deploying the Atlassian Companion app to all end users. I need to get rid of the prompt for user to allow the site:

The online documentation says to use COMPANION_TRUSTED_DOMAINS=“https://...", but that is not working for me. I can see that the Environment Variable is being created in Windows, but Chrome is still prompts. How do we fix this???

Thanks,

James

Accepted answers

Alex K

Hi @James Fenton ,

This dialog is entirely handled by the web browser. The custom protocol handler is associated with Companion at the operating system level, but the browser has an additional confirmation. In this case, for Google Chrome, it looks like default custom protocol handlers can be configured: see this article.

Regards,
Alex K

All comments

Alex K

Hi @James Fenton ,

Regards,
Alex K

James Fenton

Hi @Alex K ,

Thanks for your reply. It looks like your suggestion applies to Chrome for Enterprise which we are not using. How can I get this done with regular Chrome? Why doesn't the info that Atlassian suggested work?

Thanks,

James

Alex K

@James Fenton

This is not related to Companion itself, as I said this is browser behaviour. Changing settings in Companion cannot resolve this.

Companion itself has an extra layer of security where it asks the user to trust the source domain of requests. Setting COMPANION_TRUSTED_DOMAINS means domains are already trusted and hence this Companion dialog will not be shown. This has nothing to do with the dialog you have shared in this post.

James Fenton

@Alex K Thanks for the response and explanation. Any chance you know the protocol handler for the Companion? I think this issue will be resolved if I incorporate that. "atlassian-companion://" doesn't seem to be valid.

Thanks,

James

Welcome!

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

Quick Links

Find more posts tagged with

confluence

server

confluence-server

companion-app

trust