[jira] [Updated] (CAMEL-12602) Camel Wordpress don't set basic authentication even if user and password are provided
[
https://issues.apache.org/jira/browse/CAMEL-12602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ricardo Zanini updated CAMEL-12602:
---
Description:
When setting user/password for Basic Authentication, the component misses
adding the HTTP headers to perform the actual authentication.
Users should see the following message in logs, even though the user/pass
properties are set:
{{2018-06-27 17:20:16 [main] WARN o.a.c.c.w.p.WordpressPostProducer - Wordpress
Producer hasn't authentication. This may lead to errors during route execution.
Wordpress writing operations need authentication.}}
was:
When setting user/password for Basic Authentication, the component misses
adding the HTTP headers to perform the actual authentication.
Users should see the following message in logs, even though the user/pass
properties are set:
~~~
2018-06-27 17:20:16 [main] WARN o.a.c.c.w.p.WordpressPostProducer - Wordpress
Producer hasn't authentication. This may lead to errors during route execution.
Wordpress writing operations need authentication.
~~~
> Camel Wordpress don't set basic authentication even if user and password are
> provided
> -
>
> Key: CAMEL-12602
> URL: https://issues.apache.org/jira/browse/CAMEL-12602
> Project: Camel
> Issue Type: Bug
> Components: camel-wordpress
>Affects Versions: 2.21.0
>Reporter: Ricardo Zanini
>Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When setting user/password for Basic Authentication, the component misses
> adding the HTTP headers to perform the actual authentication.
> Users should see the following message in logs, even though the user/pass
> properties are set:
> {{2018-06-27 17:20:16 [main] WARN o.a.c.c.w.p.WordpressPostProducer -
> Wordpress Producer hasn't authentication. This may lead to errors during
> route execution. Wordpress writing operations need authentication.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12602) Camel Wordpress don't set basic authentication even if user and password are provided
Ricardo Zanini created CAMEL-12602: -- Summary: Camel Wordpress don't set basic authentication even if user and password are provided Key: CAMEL-12602 URL: https://issues.apache.org/jira/browse/CAMEL-12602 Project: Camel Issue Type: Bug Components: camel-wordpress Affects Versions: 2.21.0 Reporter: Ricardo Zanini When setting user/password for Basic Authentication, the component misses adding the HTTP headers to perform the actual authentication. Users should see the following message in logs, even though the user/pass properties are set: ~~~ 2018-06-27 17:20:16 [main] WARN o.a.c.c.w.p.WordpressPostProducer - Wordpress Producer hasn't authentication. This may lead to errors during route execution. Wordpress writing operations need authentication. ~~~ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12201) camel-wordpress: add support for JWT authentication
[ https://issues.apache.org/jira/browse/CAMEL-12201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ricardo Zanini updated CAMEL-12201: --- Fix Version/s: Future > camel-wordpress: add support for JWT authentication > --- > > Key: CAMEL-12201 > URL: https://issues.apache.org/jira/browse/CAMEL-12201 > Project: Camel > Issue Type: New Feature >Reporter: Ricardo Zanini >Priority: Major > Labels: camel-wordpress, wordpress > Fix For: Future > > Original Estimate: 504h > Remaining Estimate: 504h > > `camel-wordpress` supports only Basic Authentication, which isn't the best > approach for production environments. > For this to work, the plugin [JWT > Authentication|https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/] > must be installed on Wordpress. > There's a lot of plugins that implement JWT Authentication, but this one > seems [more > reliable|https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/#authentication-plugins] > and that's the one with more updates and stars. So, we should stick to it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12201) camel-wordpress: add support for JWT authentication
Ricardo Zanini created CAMEL-12201: -- Summary: camel-wordpress: add support for JWT authentication Key: CAMEL-12201 URL: https://issues.apache.org/jira/browse/CAMEL-12201 Project: Camel Issue Type: New Feature Reporter: Ricardo Zanini `camel-wordpress` supports only Basic Authentication, which isn't the best approach for production environments. For this to work, the plugin [JWT Authentication|https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/] must be installed on Wordpress. There's a lot of plugins that implement JWT Authentication, but this one seems [more reliable|https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/#authentication-plugins] and that's the one with more updates and stars. So, we should stick to it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12138) Expose Braintree Dispute API
[ https://issues.apache.org/jira/browse/CAMEL-12138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339791#comment-16339791 ] Ricardo Zanini commented on CAMEL-12138: [~nofuss] are you working on it? > Expose Braintree Dispute API > > > Key: CAMEL-12138 > URL: https://issues.apache.org/jira/browse/CAMEL-12138 > Project: Camel > Issue Type: New Feature > Components: camel-braintree >Reporter: Russ Johnson >Priority: Major > Fix For: 2.21.0 > > > Braintree's Dispute API, described here: > https://developers.braintreepayments.com/reference/response/dispute/java, is > not currently exposed in the Braintree Component. > The intention of this ticket is to expose the Braintree Dispute API in the > Component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12192) BindyCsvDataFormat does not support skip fields
[ https://issues.apache.org/jira/browse/CAMEL-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339712#comment-16339712 ] Ricardo Zanini commented on CAMEL-12192: [~neoxu999] are you working on a PR? > BindyCsvDataFormat does not support skip fields > > > Key: CAMEL-12192 > URL: https://issues.apache.org/jira/browse/CAMEL-12192 > Project: Camel > Issue Type: Improvement > Components: camel-bindy >Affects Versions: 2.20.1 >Reporter: Neo Xu >Priority: Major > Original Estimate: 48h > Remaining Estimate: 48h > > Currently: BindyCsvDataFormat has to map all the fields in a CSV file. > If there are 200 fields in a CSV file, it has to create 200 fields in a > class. But sometimes, it is only interested in 20 fields. So it needs to skip > some positions if they are not required. But BindyCsvDataFormat will throw an > exception in this case. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12183) Add support for Wordpress REST API
Ricardo Zanini created CAMEL-12183: -- Summary: Add support for Wordpress REST API Key: CAMEL-12183 URL: https://issues.apache.org/jira/browse/CAMEL-12183 Project: Camel Issue Type: New Feature Reporter: Ricardo Zanini Wordpress is on 29% of the web, meaning that there are a lot of people over there looking for integration with their systems. I can think of use cases like users synchronization with other data sources, automatic post, migrations, reports creations and so on. Although where it could be really shine is on e-commerce web sites built on top of Wordpress. Camel could integrate the e-commerce platform with a CRM or an ERP, for example. Anyway, I think this component may see many uses. [I'm already on it|https://github.com/m88i/camel-wordpress] and should send a PR in a couple hours. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12132) camel-snmp v3 should provide pooling for multiple endpoint / user authentication
Ricardo Zanini created CAMEL-12132: -- Summary: camel-snmp v3 should provide pooling for multiple endpoint / user authentication Key: CAMEL-12132 URL: https://issues.apache.org/jira/browse/CAMEL-12132 Project: Camel Issue Type: Improvement Components: camel-snmp Affects Versions: 2.20.1 Reporter: Ricardo Zanini Priority: Minor we want to use camel with multiple polling endpoints of type SNMP. The restrictions we have are: - snmp version 3 with authentication and privacy - each endpoint might have different credentials und securityName (user). When we configure two endpoint with the URIs snmp:192.168.56.101:161?snmpVersion=3=POLL=1.3.6.1.2.1.7.5.1==SHA1 ==PrivAES128=secname111=3 and snmp:192.168.56.102:1612?snmpVersion=3=POLL=1.3.6.1.2.1.7.5.1==SHA1 ==PrivAES128=secname222=3 We get exceptions when polling the first endpoint 2018-01-08 13:05:12.124 WARN 3076 --- [.168.56.101:161] o.a.c.c.s.SnmpOIDPoller : Consumer Consumer[snmp://192.168.56.101:161?authenticationPassphrase=xx=SHA1=1.3.6.1.2.1.7.5.1=xx=AES128=3= secname111=3=POLL] failed polling endpoint: snmp://udp:192.168.56.101/161. Will try again at next poll. Caused by: [org.snmp4j.MessageException - Message processing model 3 returned error: Unknown security name] org.snmp4j.MessageException: Message processing model 3 returned error: Unknown security name at org.snmp4j.MessageDispatcherImpl.sendPdu(MessageDispatcherImpl.java:520) ~[snmp4j-2.5.0.jar:?] at org.snmp4j.Snmp.sendMessage(Snmp.java:1059) ~[snmp4j-2.5.0.jar:?] at org.snmp4j.Snmp.send(Snmp.java:1029) ~[snmp4j-2.5.0.jar:?] at org.snmp4j.Snmp.send(Snmp.java:1013) ~[snmp4j-2.5.0.jar:?] at org.apache.camel.component.snmp.SnmpOIDPoller.poll(SnmpOIDPoller.java:176) ~[camel-snmp-2.19.4.jar:2.19.4] at org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174) [camel-core-2.19.4.jar:2.19.4] at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101) [camel-core-2.19.4.jar:2.19.4] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_112] at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [?:1.8.0_112] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) [?:1.8.0_112] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:1.8.0_112] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_112] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_112] at java.lang.Thread.run(Unknown Source) [?:1.8.0_112] It seems that after configuration of the second endpoint the security information of the first endpoint is not found/used anymore. See Nabble: http://camel.465427.n5.nabble.com/Bug-in-component-camel-snmp-td5816536.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12123) camel-salesforce - Http proxy support uses two inconsistent methods and is broken
[ https://issues.apache.org/jira/browse/CAMEL-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316227#comment-16316227 ] Ricardo Zanini commented on CAMEL-12123: I could work on this. Waiting for triage. :) > camel-salesforce - Http proxy support uses two inconsistent methods and is > broken > - > > Key: CAMEL-12123 > URL: https://issues.apache.org/jira/browse/CAMEL-12123 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 2.20.1 >Reporter: Mabrouk Belhout > Labels: proxy, salesforce > > in the SalesforceComponent class, there is two ways to configure a http proxy > : > - using setHttpProxyHost method and others alike > - using httpClientProperties map with proxy keys (HTTP_PROXY_HOST and others > ...) > but instance variables set by setHttpProxyXXX methods are not used and should > be considered as dead code. > one can have a look at the setupHttpClient() method to figure out that the > proxy variables are not used, but only the properties map is. > This bug was discovered while proceeding to an upgrade from 2.19.x to 2.20.1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-9260) Dataformat Apache Any23
[ https://issues.apache.org/jira/browse/CAMEL-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308255#comment-16308255 ] Ricardo Zanini commented on CAMEL-9260: --- [~gautric] are you still working on this? Do you mind to share your ideas or what have you been doing, so I may work with you? > Dataformat Apache Any23 > --- > > Key: CAMEL-9260 > URL: https://issues.apache.org/jira/browse/CAMEL-9260 > Project: Camel > Issue Type: New Feature >Reporter: Greg A. >Priority: Minor > > Apache Any23 is the official Microformat lib. > We could implements this lib as a Dataformat feature. > I am working to understand what we could include for the first release. > http://any23.apache.org/ > http://any23.apache.org/getting-started.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11474) Camel-Hipchat: Allow configurable http client
[ https://issues.apache.org/jira/browse/CAMEL-11474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308056#comment-16308056 ] Ricardo Zanini commented on CAMEL-11474: PR sent https://github.com/apache/camel/pull/2157 > Camel-Hipchat: Allow configurable http client > - > > Key: CAMEL-11474 > URL: https://issues.apache.org/jira/browse/CAMEL-11474 > Project: Camel > Issue Type: Improvement > Components: camel-hipcat >Affects Versions: 2.19.1 >Reporter: Paul Watson >Priority: Minor > > As it stands the Hipchat component uses a sealed private static final to > define the apache http client for communication. It would be great if we > could allow a more configurable client. > One such prominent use-case here is on-premise versions of Hipchat using > private certificates that need configuring on the SSLContext. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-9260) Dataformat Apache Any23
[ https://issues.apache.org/jira/browse/CAMEL-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294829#comment-16294829 ] Ricardo Zanini commented on CAMEL-9260: --- [~davsclaus] they released a version in [September, 17|https://mvnrepository.com/artifact/org.apache.any23/apache-any23-core]. I may work on a PR. > Dataformat Apache Any23 > --- > > Key: CAMEL-9260 > URL: https://issues.apache.org/jira/browse/CAMEL-9260 > Project: Camel > Issue Type: New Feature >Reporter: Greg A. >Priority: Minor > > Apache Any23 is the official Microformat lib. > We could implements this lib as a Dataformat feature. > I am working to understand what we could include for the first release. > http://any23.apache.org/ > http://any23.apache.org/getting-started.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (CAMEL-12080) Allow creating csv content without last eol
[ https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ricardo Zanini updated CAMEL-12080: --- Comment: was deleted (was: Pull request sent: https://github.com/apache/camel/pull/2149) > Allow creating csv content without last eol > --- > > Key: CAMEL-12080 > URL: https://issues.apache.org/jira/browse/CAMEL-12080 > Project: Camel > Issue Type: Improvement > Components: camel-bindy >Reporter: Marcin Domanski >Priority: Minor > Fix For: Future > > > Hello, > rfc4180 for CSV states: > bq. The last record in the file may or may not have an ending line break. > For deserialization Bindy accepts both types of files, but for serialization > Bindy to my knowledge always creates content with last row ending with > newline. Unfortunately some legacy systems treat last newline as one more > empty row. Would it be possible to introduce control over this? I have this > problem in CSV and also in fixed format for one other place. For now we need > to strip the last char in Camel processor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
