[ 
https://issues.apache.org/jira/browse/NIFI-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150781#comment-15150781
 ] 

ASF GitHub Bot commented on NIFI-1521:
--------------------------------------

Github user pvillard31 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/232#discussion_r53195449
  
    --- Diff: 
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AbstractAMQPProcessor.java
 ---
    @@ -84,6 +89,72 @@
                 .allowableValues("0.9.1")
                 .defaultValue("0.9.1")
                 .build();
    +    public static final PropertyDescriptor USE_SSL_PROTOCOL = new 
PropertyDescriptor.Builder()
    +            .name("Use SSL protocol")
    +            .description("Indicates whether or not SSL protocol should be 
used")
    +            .allowableValues("true", "false")
    +            .defaultValue("false")
    +            .required(true)
    +            .build();
    +    public static final PropertyDescriptor VALIDATE_CERTIFICATES = new 
PropertyDescriptor.Builder()
    --- End diff --
    
    @alopresto In fact I added this possibility because this is a use case 
described in [the RabbitMQ documentation](https://www.rabbitmq.com/ssl.html), 
and I assumed this is a possible scenario. Regarding the default value, I 
definitely agree with you, my bad.


> Allow SSL with AMQP processors
> ------------------------------
>
>                 Key: NIFI-1521
>                 URL: https://issues.apache.org/jira/browse/NIFI-1521
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.5.0
>            Reporter: Pierre Villard
>            Priority: Trivial
>              Labels: beginner
>             Fix For: 0.6.0
>
>
> AMQP processor shall allow the creation of connections using SSL protocol 
> (not necessarily with presenting and validating certificates)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to