Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The purpose of ResourceAPI #35

Open
CelestialArcadia opened this issue Dec 27, 2021 · 0 comments
Open

The purpose of ResourceAPI #35

CelestialArcadia opened this issue Dec 27, 2021 · 0 comments

Comments

@CelestialArcadia
Copy link

Hello!

I didn't know how else I would reach you, but I have been trying to wrap my head around the "ResourceAPI" purpose,
and it's still not clear to me.

  1. When the angular app trying to communicate with the backend, why not just do so directly with the AuthServer.
  2. And in case I wanted my angular app to communicate with the backend, then the URI should include the "API/controller" in the "ValuesController" class then add - say the "register" URI? it's still confusing, and especially how it ( the resource API ) redirects to "AuthSever".
  3. is it playing like some sort of a gateway? if so, should I configure it if I had to add some logic? - To be more specific in what situation(s) the resourceAPI will serve me.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant