JHipster problem with frontend/gateway communication











up vote
0
down vote

favorite












following the explanation on separating frontend and gateway, I created two JHipster applications:




  • Gateway using jhipster --skip-client

  • Frontend using jhipster --skip-server --db --auth uaa --uaa-base-name uaa-server


When using Swagger-UI, I can use the default API and the API of my UAA server. I can also see in the drop-down menu my micro-services but when selecting them, I get an error message :




Can't read swagger JSON from http://127.0.0.1:9000/myservice/v2/api-docs




What is wrong in my configuration ? What did I forget ?



[EDIT] I finally found, see below



The second question is about the communication between frontend and gateway when both are running on different machines.
Authentication seems to be correct when looking at UAA server but frontend side receives a 403 code. It seems to be a problem with CSRF but I don't know how to handle it.
What's the way to deal with CSRF in JHipster ?



PS : I'm pretty sure I will also have problem when making to microservices talk together :)










share|improve this question




























    up vote
    0
    down vote

    favorite












    following the explanation on separating frontend and gateway, I created two JHipster applications:




    • Gateway using jhipster --skip-client

    • Frontend using jhipster --skip-server --db --auth uaa --uaa-base-name uaa-server


    When using Swagger-UI, I can use the default API and the API of my UAA server. I can also see in the drop-down menu my micro-services but when selecting them, I get an error message :




    Can't read swagger JSON from http://127.0.0.1:9000/myservice/v2/api-docs




    What is wrong in my configuration ? What did I forget ?



    [EDIT] I finally found, see below



    The second question is about the communication between frontend and gateway when both are running on different machines.
    Authentication seems to be correct when looking at UAA server but frontend side receives a 403 code. It seems to be a problem with CSRF but I don't know how to handle it.
    What's the way to deal with CSRF in JHipster ?



    PS : I'm pretty sure I will also have problem when making to microservices talk together :)










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      following the explanation on separating frontend and gateway, I created two JHipster applications:




      • Gateway using jhipster --skip-client

      • Frontend using jhipster --skip-server --db --auth uaa --uaa-base-name uaa-server


      When using Swagger-UI, I can use the default API and the API of my UAA server. I can also see in the drop-down menu my micro-services but when selecting them, I get an error message :




      Can't read swagger JSON from http://127.0.0.1:9000/myservice/v2/api-docs




      What is wrong in my configuration ? What did I forget ?



      [EDIT] I finally found, see below



      The second question is about the communication between frontend and gateway when both are running on different machines.
      Authentication seems to be correct when looking at UAA server but frontend side receives a 403 code. It seems to be a problem with CSRF but I don't know how to handle it.
      What's the way to deal with CSRF in JHipster ?



      PS : I'm pretty sure I will also have problem when making to microservices talk together :)










      share|improve this question















      following the explanation on separating frontend and gateway, I created two JHipster applications:




      • Gateway using jhipster --skip-client

      • Frontend using jhipster --skip-server --db --auth uaa --uaa-base-name uaa-server


      When using Swagger-UI, I can use the default API and the API of my UAA server. I can also see in the drop-down menu my micro-services but when selecting them, I get an error message :




      Can't read swagger JSON from http://127.0.0.1:9000/myservice/v2/api-docs




      What is wrong in my configuration ? What did I forget ?



      [EDIT] I finally found, see below



      The second question is about the communication between frontend and gateway when both are running on different machines.
      Authentication seems to be correct when looking at UAA server but frontend side receives a 403 code. It seems to be a problem with CSRF but I don't know how to handle it.
      What's the way to deal with CSRF in JHipster ?



      PS : I'm pretty sure I will also have problem when making to microservices talk together :)







      jhipster csrf-protection csrf-token






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 23 at 12:57

























      asked Nov 22 at 16:13









      Frédéric Praca

      479411




      479411
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          Added contexts for proxying in webpack.dev.js and it seems to be working.






          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',
            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%2f53434805%2fjhipster-problem-with-frontend-gateway-communication%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            Added contexts for proxying in webpack.dev.js and it seems to be working.






            share|improve this answer

























              up vote
              1
              down vote













              Added contexts for proxying in webpack.dev.js and it seems to be working.






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                Added contexts for proxying in webpack.dev.js and it seems to be working.






                share|improve this answer












                Added contexts for proxying in webpack.dev.js and it seems to be working.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 at 16:40









                Frédéric Praca

                479411




                479411






























                    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%2f53434805%2fjhipster-problem-with-frontend-gateway-communication%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

                    What visual should I use to simply compare current year value vs last year in Power BI desktop

                    How to ignore python UserWarning in pytest?

                    Alexandru Averescu