Jhipster网关用户如何才能仅从登录用户的服务中获取实体

Question

I'm using jhipster microservices to build my project called Sport Stat application. I have used jhipster to generate the following spring boot backend only microservices:

• PlayerStatService
• LeagueService

The PlayerStatService has several entities such as Sport, Skill, Player and so on. Each player can have a list of Sessions, Targets and etc.

Sports and Skills are all predefined.

I also have generated a gateway client that communicates with the above services securely. You can sign up and register yourself as a User on the Gateway (client). A user can a be Coach who is monitoring his players. A coach can add a new player(s) and start monitoring and tracking their stats. A coach can have many players (one-to-many).

Logged-in users (Coaches) should view their players and their stats only, NOT everybody else's. I assume I can have entity relationship between Player and User so that I can use findByUserIsCurrentUser to get the current user players and stats.

I know this can be used easily if it a monolithic application.

Problem: Because the User is generated by jhipster on gateway and Player is on PlayerStatService, I cannot create any relationship between them. I get this error.

Your entity cannot have a relationship with User because it's a gateway entity

My Question: Is it possible to achieve such a thing by using the generated classes and objects (Service, Repository)?

If not, how would you suggest, for example: to restrict Users to be able to get their own players ONLY? When calling the PlayerStatService RestAPI to get players how do you suggest I should incorporate the logged-in user in my query at the repository level?

EDITED: I am using JWT as Authentication

Answer 1

This cannot be done in gateway, it must be done in services and ideally only based on the data contained in the token: subject, roles or other claims so that your services don't need to query your gateway or auth provider.

As you have seen this can't be done using relationships with User, however you can add a user_id simple field to your entities and match it against token's subject.

Roles are useful also to restrict access but if they are not enough to model that user is belonging to a team, you can add team_id as a claim to your token. This way you can easily identify a coach because she/he has ROLE_COACH and for which team she/he is in this role.