Secure Nifi with SSL












0














I secure successfully a Nifi Node (localhost) with SSL but I have always a yellow padlock in my browser as you can see in the pic here
Do you have any idea?
Thanks










share|improve this question



























    0














    I secure successfully a Nifi Node (localhost) with SSL but I have always a yellow padlock in my browser as you can see in the pic here
    Do you have any idea?
    Thanks










    share|improve this question

























      0












      0








      0







      I secure successfully a Nifi Node (localhost) with SSL but I have always a yellow padlock in my browser as you can see in the pic here
      Do you have any idea?
      Thanks










      share|improve this question













      I secure successfully a Nifi Node (localhost) with SSL but I have always a yellow padlock in my browser as you can see in the pic here
      Do you have any idea?
      Thanks







      ssl ssl-certificate apache-nifi






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 12 at 14:06









      Z A

      32




      32
























          2 Answers
          2






          active

          oldest

          votes


















          1














          If you used a self-signed certificate then this is expected behavior. You would have to purchase a real certificate for a real domain name in order for the browser to not warn you.






          share|improve this answer





















          • Thanks Bryan I've another question please (you can see it here: community.hortonworks.com/questions/226357/…)
            – Z A
            Nov 13 at 15:13



















          0














          I see the description below:

          Standalone : generates the certificate authority, keystores, truststores, and nifi.properties files in one command



          Client/Server mode : uses a Certificate Authority Server that accepts Certificate Signing Requests from clients, signs them, and sends the resulting certificates back. Both client and server validate the other’s identity through a shared secret.



          Standalone and client, both generate the certificate authority, keystores, truststores.
          Sorry, I don't see the difference.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263855%2fsecure-nifi-with-ssl%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            If you used a self-signed certificate then this is expected behavior. You would have to purchase a real certificate for a real domain name in order for the browser to not warn you.






            share|improve this answer





















            • Thanks Bryan I've another question please (you can see it here: community.hortonworks.com/questions/226357/…)
              – Z A
              Nov 13 at 15:13
















            1














            If you used a self-signed certificate then this is expected behavior. You would have to purchase a real certificate for a real domain name in order for the browser to not warn you.






            share|improve this answer





















            • Thanks Bryan I've another question please (you can see it here: community.hortonworks.com/questions/226357/…)
              – Z A
              Nov 13 at 15:13














            1












            1








            1






            If you used a self-signed certificate then this is expected behavior. You would have to purchase a real certificate for a real domain name in order for the browser to not warn you.






            share|improve this answer












            If you used a self-signed certificate then this is expected behavior. You would have to purchase a real certificate for a real domain name in order for the browser to not warn you.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 12 at 14:19









            Bryan Bende

            10.3k816




            10.3k816












            • Thanks Bryan I've another question please (you can see it here: community.hortonworks.com/questions/226357/…)
              – Z A
              Nov 13 at 15:13


















            • Thanks Bryan I've another question please (you can see it here: community.hortonworks.com/questions/226357/…)
              – Z A
              Nov 13 at 15:13
















            Thanks Bryan I've another question please (you can see it here: community.hortonworks.com/questions/226357/…)
            – Z A
            Nov 13 at 15:13




            Thanks Bryan I've another question please (you can see it here: community.hortonworks.com/questions/226357/…)
            – Z A
            Nov 13 at 15:13













            0














            I see the description below:

            Standalone : generates the certificate authority, keystores, truststores, and nifi.properties files in one command



            Client/Server mode : uses a Certificate Authority Server that accepts Certificate Signing Requests from clients, signs them, and sends the resulting certificates back. Both client and server validate the other’s identity through a shared secret.



            Standalone and client, both generate the certificate authority, keystores, truststores.
            Sorry, I don't see the difference.






            share|improve this answer


























              0














              I see the description below:

              Standalone : generates the certificate authority, keystores, truststores, and nifi.properties files in one command



              Client/Server mode : uses a Certificate Authority Server that accepts Certificate Signing Requests from clients, signs them, and sends the resulting certificates back. Both client and server validate the other’s identity through a shared secret.



              Standalone and client, both generate the certificate authority, keystores, truststores.
              Sorry, I don't see the difference.






              share|improve this answer
























                0












                0








                0






                I see the description below:

                Standalone : generates the certificate authority, keystores, truststores, and nifi.properties files in one command



                Client/Server mode : uses a Certificate Authority Server that accepts Certificate Signing Requests from clients, signs them, and sends the resulting certificates back. Both client and server validate the other’s identity through a shared secret.



                Standalone and client, both generate the certificate authority, keystores, truststores.
                Sorry, I don't see the difference.






                share|improve this answer












                I see the description below:

                Standalone : generates the certificate authority, keystores, truststores, and nifi.properties files in one command



                Client/Server mode : uses a Certificate Authority Server that accepts Certificate Signing Requests from clients, signs them, and sends the resulting certificates back. Both client and server validate the other’s identity through a shared secret.



                Standalone and client, both generate the certificate authority, keystores, truststores.
                Sorry, I don't see the difference.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 at 15:14









                Z A

                32




                32






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263855%2fsecure-nifi-with-ssl%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Xamarin.iOS Cant Deploy on Iphone

                    Glorious Revolution

                    Dulmage-Mendelsohn matrix decomposition in Python