is an opinionated boilerplate for single-page application development based on .NET Core, Kestrel, GraphQL on the backend and React, Redux, Babel, Webpack on the frontend
so, in your case, what approach did you have on the auth problem, cookie or tokens ?
With a token-based authentication, I think you would still need to send it as a cookie, e.g. user enters username/password, clicks Login, that infor is sent to /token endpiont via Ajax, that endpoint generates a new token and sends it to the client in an HTTPOnly cookie (
id_token), all subsequent requests to the server will send that token automatically. Then on the server, there should be a middleware that reads cookies.id_token value if it exists, decods it into a User object and puts it into request context so that all the remaining middlewares down the pipeline for that particular request have access to a decoded User object. On the client, if /token endpoint returned "true" or something like that, you can just redirect a user from the /login page to /dashboard etc. window.location.href = '/dashboard',
deployed the app to azure
using local git
but it gives me a HTTP Error 502.5 - Process Failure
Common causes of this issue:
The application process failed to start
The application process started but then stopped
The application process started but failed to listen on the configured port
what am i doing wrong?
1.0.1* sorry
Or it uses same webpack/hot reload/etc things as fb boilerplate?
reactjs newbie here - just downloaded the aspnet startet kit (fantastic work!) - what's the preferred way to scaffold components?
In addition, I went into VS Code and launched from there. re npm intall'd like it was a new project, but same thing.
