You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenHMIS API now supports authentication, so the client app needs to do the same. I hinted at this in #32, but this is the explicit issue.
We won't set up a proper workflow for this right now, but eventually we probably want to add a sign-in page before the search page. Only authenticated users will be able to make API requests.
The text was updated successfully, but these errors were encountered:
Link to the explanation of how to get a Google client ID for
authentication. Save this ID in a config file. Store the generated
client_id in the page and use it for signin.
Since the client-side javascript already needed to have this client_id,
I don't think that embedding it in the page is a problem.
To make this work: add a login page in front of the search/home page that calls out to Google/the API, just like the signup page on the OpenHMIS server itself. Once the user has authenticated, use the returned id token in all requests to the API (that is, add an authorization header to each request in client.server.controller.js).
The OpenHMIS API now supports authentication, so the client app needs to do the same. I hinted at this in #32, but this is the explicit issue.
We won't set up a proper workflow for this right now, but eventually we probably want to add a sign-in page before the search page. Only authenticated users will be able to make API requests.
The text was updated successfully, but these errors were encountered: