I have created jhipster microservice app without any registry or gateway as I will be using aws managed gateway.
But I don't see the swagger ui.
Related
We have separated frontend and backend and used the jhipster --skip-server command to create frontend and used jhipster --skip-client to create backend service.
Now we would like to add more entities to frontend and backend.
So, how to generate separate frontend and backend code for an entity?
Gateway is the only backend service we have now. Postgres is our relational database.
jHipster registry is also installed to monitor services.
I setup the following components using Jhipster (version of generator-jhipster: # 5.0.1)
Gateway
Microservice1
Jhipster Registry
Keycloak as auth server
Everything works fine so far.
In Jhipster Registry, when I go to Administration >> API
It opens up Swagger UI. Swagger UI lists the apis for Jhipster-Registry and gateway. But it gives error when the microservice is selected in the drop down. Swagger UI From Gateway (Administration >> API) works fine. Only from registry it does not work.
Please let me know if I am missing some configuration.
When using the JHipster Registry to manage an OAuth2 microservice architecture, you need to enable the oauth2 profile when running the JHipster Registry. You will then use Keycloak to log in to the registry and manage the services.
I setup the following components using Jhipster (version of generator-jhipster: # 5.3.1)
Gateway
Jhipster Registry
UAA Server
Everything works fine so far.
In Jhipster Registry, when I go to Administration >> API It opens up Swagger UI. Swagger UI lists the apis for Jhipster-Registry only. But it gives error when the uaa or gateway is selected in the drop down. Swagger UI From Gateway (Administration >> API) works fine. Only from registry it does not work.
Please let me know if I am missing some configuration.
UAA support for the registry was just recently added and will be in the next release. If you want to have it early, you can make the following changes:
In your UAA app's UaaConfiguration.java, add .authorities("ROLE_ADMIN") here.
Then you can use the develop tag for the jhipster-registry Docker image, and add the uaa profile to that container's SPRING_ACTIVE_PROFILES
If you prefer to run the JHipster Registry from source, you can clone the jhipster-registry repository and check out the develop branch
I developed a microservice application with these :
Jhipster registry
Uaa
Gateway
Microservice1
I want to deploy this in production on different server, but I don't want to use IP to access to microservices.
How can I launch microservice1 and uaa to say to the registry that they need to be called with these URLs :
uaa.myapp.com
microservice1.myapp.com
Is there a way to configure JHipster microservice application with the Cloudfoundry UAA?
During generation of microservice application with Yeoman JHipster generator it gives us an option to select UAA application provided by JHipster for authentication. However I don't want to use UAA application provided by JHipster.
I have other applications in cloudfoundry which use UAA instance provided by Cloudfoundry. So I want to configure the same with JHipster.
Any help is appreciated.