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 :)
jhipster csrf-protection csrf-token
asked Nov 22 at 16:13
Frédéric Praca
479411
add a comment |
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 :)
jhipster csrf-protection csrf-token
asked Nov 22 at 16:13
Frédéric Praca
479411
add a comment |
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 :)
jhipster csrf-protection csrf-token
asked Nov 22 at 16:13
Frédéric Praca
479411
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
jhipster csrf-protection csrf-token
asked Nov 22 at 16:13
Frédéric Praca
479411
asked Nov 22 at 16:13
Frédéric Praca
479411
edited Nov 23 at 12:57
asked Nov 22 at 16:13
Frédéric Praca
479411
asked Nov 22 at 16:13
Frédéric Praca
479411
asked Nov 22 at 16:13
Frédéric Praca
479411
479411
add a comment |
add a comment |
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.
answered Nov 22 at 16:40
Frédéric Praca
479411
add a comment |
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.
answered Nov 22 at 16:40
Frédéric Praca
479411
add a comment |
up vote
1
down vote
Added contexts for proxying in webpack.dev.js and it seems to be working.
answered Nov 22 at 16:40
Frédéric Praca
479411
add a comment |
up vote
1
down vote
up vote
1
down vote
Added contexts for proxying in webpack.dev.js and it seems to be working.
answered Nov 22 at 16:40
Frédéric Praca
479411
Added contexts for proxying in webpack.dev.js and it seems to be working.
answered Nov 22 at 16:40
Frédéric Praca
479411
answered Nov 22 at 16:40
Frédéric Praca
479411
answered Nov 22 at 16:40
Frédéric Praca
479411
answered Nov 22 at 16:40
Frédéric Praca
479411
479411
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
