Marcelo Shima

The errors happens on microfrontend side (not gateway) with oauth2. User was wrongly been exposed by the microfrontend. Exposing entities are not required anymore.

@mraible no, the PR https://github.com/jhipster/generator-jhipster/pull/19357 should fix the issue. > For the case above user entity is not required but if user has relationship with some of the entitles user...

@mraible weblux+neo4j is broken for almost 6 months. And were flaky before that. https://github.com/hipster-labs/jhipster-daily-builds/actions/workflows/neo4j.yaml?page=7 Do you think I should test user relationships using another database?

@mraible user api is always using gateways api, it may not be synchronized. Not sure if https://github.com/jhipster/generator-jhipster/pull/19382 fixes user issues.

@mraible I did some test with `syncUserWithIdP`. It's not compatible with microfrontends and microservices (gateways should work). The synchronization happens here https://github.com/jhipster/generator-jhipster/blob/9f478679d9f59ef891243399809479fd93772386/generators/server/templates/src/main/java/package/web/rest/AccountResource.java.ejs#L78 It's executed when the current account is fetched,...

The AccountResource doesn't exists at microservices.

@mraible should be fixed at the PR, but it's useless without the backend support. Should we fail when a user relationship is found at Microservices?

Ought I think the examples worked because you are using neo4j. At the form, the user is loaded using the gateway api. Neo4j cascades, so the user entity (which was...

@mraible implemented the syncUser logic at the /api/users api for Microservices at https://github.com/jhipster/generator-jhipster/pull/19384. User relationships are ok. Generated using Postgres: ``` jhipster jdl reactive-mf.jdl --client-framework angularX --workspaces --monorepository --db postgresql...

I've done some design changes to angular sort icons recently, you may be interested https://github.com/jhipster/generator-jhipster/pull/19371.