[jira] [Updated] (CONNECTORS-1736) LDAP Mapper: attribute condition

2022-10-05 Thread Julien Massiera (Jira)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien Massiera updated CONNECTORS-1736:

Component/s: LDAP Mapper
 (was: LDAP authority)

> LDAP Mapper: attribute condition
> 
>
> Key: CONNECTORS-1736
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1736
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: LDAP Mapper
>Affects Versions: ManifoldCF 2.23
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Fix For: ManifoldCF 2.24
>
>
> Sometimes, the user mapping may depends on a specific attribute value. It 
> would be good to provide a way to configure a mapping condition, based on an 
> LDAP attribute matching a regexp, that will determine the final mapping to 
> perform. 



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


[jira] [Resolved] (CONNECTORS-1737) Suggestion for adding function for proxy configuration for connector of Confluence-V6

2022-10-05 Thread Karl Wright (Jira)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-1737.
-
Fix Version/s: ManifoldCF 2.24
   Resolution: Fixed

r1904412.


> 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
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.24
>
> 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. +*Suggested source code (based on release 2.22.1)*+
> 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)


[jira] [Assigned] (CONNECTORS-1737) Suggestion for adding function for proxy configuration for connector of Confluence-V6

2022-10-05 Thread Karl Wright (Jira)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-1737:
---

Assignee: Karl Wright

> 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
>Assignee: Karl Wright
>Priority: Major
> 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. +*Suggested source code (based on release 2.22.1)*+
> 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)