Nguyen Huu Nhat created CONNECTORS-1737:
-------------------------------------------

             Summary: Suggestion for adding function for proxy configuration 
for connector of Confluence-V6
                 Key: CONNECTORS-1737
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1737
             Project: ManifoldCF
          Issue Type: Improvement
            Reporter: Nguyen Huu Nhat
         Attachments: EditConnection.png, ViewConnection.png, patch.txt

Hi there,

Currently, I am having a problem regarding the need for proxy information to 
connect to Confluence Cloud (SaaS) from the Confluence connector.
As you know, we can use Confluence Server (self-built environment) or use 
Confluence Cloud (SaaS).
Using Confluence Server, you can set up a server (for example, located in the 
same place where ManifoldCF is running) so you may not need to use proxy 
information for the connection.
However, for Confluence Cloud (SaaS), there will be cases where you need to set 
proxy information to be able to connect.

I have checked in a few other connectors of ManifoldCF, there are a few 
connectors that support setting proxy information for the connection, for 
example: SharePoint, Jira, Slack, ...
Therefore, I would like to suggest editing Confluence-v6's sourcecode 
(including Authority connector and Repository connector) so that we can have an 
option to set proxy information to use for connection to Confluence when needed.
h3. +*Connector Name*+
 - Confluence-v6 (including Authority connector and Repository connector)

h3. +*Improvement Detail*+
 - At the Confluence connection setting screen, add fields that allow the user 
to set proxy information (eg: proxyProtocol, proxyHost, proxyPort..).
The proxy setting screen will look like below:
!EditConnection.png!


 - When connecting (call method `connect()`), use the set field values as proxy 
information.

※ This improvement applies to both the Authority Connector and the Repository 
Connector side.
h3. +*Source Code Modification*+

Because the content is edited in many files and the number of LOC is quite 
large, I will attach the patch file here, please check it.
[^patch.txt]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to