Application links - creating incoming external link - We couldn't save your link

[Michał Ziemba]

I follow the article Confluence On-premises Microsoft Graph connector (preview) and I am stuck at the step 3.5 authentication type. If I want to use oAuth 2.0 and following the steps below: 

1. Go to Administration  > General configuration > Application links.
2. Select Create link
3. Select External application, and then choose Incoming as the direction.
4. Fill in the
   • Redirect URL: https://gcs.office.com/v1.0/admin/oauth/callback
   • Scope: Admin
5. Complete the connection settings step using the client ID and secret.

I also found similar guide at Confluence documentation: Configure an incoming link | Confluence Data Center 9.1 but when I try to save the link, I got an error (no matter what permission level I choose):

We couldn't save your link.
Fill in the required fields and try again. 

I have attached screenshot. I have no idea what extra fields it requires to be filled in as there is not much in the form and all is filled in. 

Do you have any suggestion how to overcome this obstacle?

Thanks in advance
Michal

[Andrew Laden]

For the historical record and any  future searches.

So I ran into the same thing. The problem turned out to be oauth2 validation failing. Because of a missing parameter in my server.xml that was set up for an nginx reverse proxy for ssl.

https://support.atlassian.com/confluence/kb/accessing-the-confluence-consent-page-as-a-part-of-oauth-20-configuration-results-in-a-tomcat-http-status-400-bad-request-error/

For those that don't want to read the whole kb article, 

for testing, first try adding following system property

-Datlassian.oauth2.provider.skip.base.url.https.requirement=true

  to your CATALINA_OPTS and restart confluence. see if it works. (you can add the link)

If it does then in your server.xml in the connector you are using add

secure="true"

You can then remove the extra system property you added for testing.

Hope that fixes it for you.

[Lukas Stürzenbecher]

Hi @Michał Ziemba 

Did you solve this issue? Currently experiencing the same thing.

@Marc - DevoteamI am connected via https but have the same problem.

[Marc - Devoteam]

Hi @Lukas Stürzenbecher 

Welcome to the community.

What are the logs providing as information?

[Lukas Stürzenbecher]

Hi

Which logs specifically? I cant find any meaninful in my instance

ls -lt
total 147484
-rw-r-----. 1 confluence confluence 1474776 Apr 1 12:52 gc-2025-03-31_16-35-02.log
-rw-r-----. 1 confluence confluence 1395397 Apr 1 12:50 conf_access_log.2025-04-01.log
-rw-r-----. 1 confluence confluence 2097290 Apr 1 12:36 gc-2025-03-31_16-35-02.log.1
-rw-r-----. 1 confluence confluence 2097206 Apr 1 12:17 gc-2025-03-31_16-35-02.log.0
-rw-r-----. 1 confluence confluence 2097265 Apr 1 11:54 gc-2025-03-31_16-35-02.log.4
-rw-r-----. 1 confluence confluence 2097247 Apr 1 11:29 gc-2025-03-31_16-35-02.log.3
-rw-r-----. 1 confluence confluence 839 Apr 1 11:28 catalina.2025-04-01.log
-rw-r-----. 1 confluence confluence 31832848 Apr 1 11:28 catalina.out
-rw-r-----. 1 confluence confluence 2097201 Apr 1 11:10 gc-2025-03-31_16-35-02.log.2

[Marc - Devoteam]

Hi @Michał Ziemba 

Check the log file docs for the correct log file.

atlassian-confluence.log

https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html 

[Marc - Devoteam]

Hi @Michał Ziemba 

I'm not a systems admin.

But AS I look at your picture, you are connecting to your Confluence on localhost.

I do think to make this work you Confluence has to run over https as well, to make the secure callback.