dmitry-n-medvedev/feather

feather's Issues

questionnaire

Design a Questionnaire layout
Design a Questionnaire Response layout

TODO:

1. replace a json file on file server with this Questionnaire.mjs
2. setup the mime type for mjs files on NGINX, remove json definition
3. the client test should request the Questionnaire.mjs, load it via fetch, and import it via "data:"

see:

1. dynamic import: https://2ality.com/2019/10/eval-via-import.html
2. https://developer.mozilla.org/en-US/docs/Web/API/Blob

Bind Token related stuff to DB

AccountToken and AccessToken creation and validation should involve using Redis as DB.

create LibTokenServer

It should issue Account and Access tokens.

Offer Service

after a client answers all the poll's questions, he should be able to post the result to /get-offer resided on the file server.

the workflow:

1. the client has the answers at hand in a form of a JSON
2. the client requests an Access Token for the next operation
3. the client issues a POST request to <file-server>/get-offer supplying the Access Token in the Authorization header
4. the NGINX of the file server authorizes the request and if successful sends it down the line to the Offer Server
5. the Offer Server should analyze the answers it receives ( not in this incarnation ) and returns an offer to the client

Refactor to use predefined Locations constants

Token Server

This should run under either PM2, or in a Docker container

Initial setup

I need initial setup of the project's layout

File Server

This should run in a Docker container.

The NGINX must be employed to serve static questionnaire json files. The NGINX must contact the Auth Server for authorization.

See: https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-subrequest-authentication/

ACL is not really required for this app

this looks like a more suitable approach

get /questionnaire.json

post /questionnaire

<function-name> <file-path>

I should be able to generate and validate an AccessToken.

{Account, Access}Token verification should be a call to a single function

Devise two functions for token verification: verifyAccountToken, and verifyAccessToken. The function should take serialized token as parameter.

FileServer

LibAuthServer

This library will be used in the AuthServer.

The AuthServer will sit behind the NGINX which will authenticate all requests to the static json files (questionnaires) under its control via the AuthServer.

See: https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-subrequest-authentication/

Auth Server

Executable.

The Auth Server authenticates requests for questionnaire static files managed by the NGINX.

The NGINX contacts the Auth Server before serving JSON files to the Client. The Auth Server sits behind the HAproxy with the token provided by the client.

NOTE: the NGINX should somehow pass the URL the Client tries to access and the Token the Client supplies.

See: https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-subrequest-authentication/

NOTE:

(see: https://nginx.org/en/docs/http/ngx_http_proxy_module.html?&_ga=2.249142535.1673781331.1610988303-447784772.1610634828#proxy_pass)

If the proxy_pass directive is specified with a URI, then when a request is passed to the server, the part of a normalized request URI matching the location is replaced by a URI specified in the directive:

location /name/ {
    proxy_pass http://127.0.0.1/remote/;
}

If proxy_pass is specified without a URI, the request URI is passed to the server in the same form as sent by a client when the original request is processed, or the full normalized request URI is passed when processing the changed URI:

location /some/path/ {
    proxy_pass http://127.0.0.1;
}

issueAccessToken

AccountToken

I should be able to generate and validate an AccountToken.