[FEAT] move authentication to the server

[zhaojzn]

frontend auth branch

[jlui17]

I think it's more reliable to get the data from the google sheet. We have some special rules for calculating this, and I don't want there to be any issues with differences between frontend and db. Let's take this out for now and we will work on bringing this later along with a few other cool changes.

[jlui17]

err can be many different errors, and we want to decipher whether its an actual system error (like the lambda failed) or if it's a user error like a code mismatch. If it's a user error, we want to return 400 status with a useful error message so it can be displayed on the frontend alert.

Please look through the SDK docs and figure out ones we should look for.
See this as an example.

[jlui17]

err can be many different errors, and we want to decipher whether its an actual system error (like the lambda failed) or if it's a user error like a code mismatch. If it's a user error, we want to return 400 status with a useful error message so it can be displayed on the frontend alert.

Please look through the SDK docs and figure out ones we should look for.
See this as an example.

[jlui17]

err can be many different errors, and we want to decipher whether its an actual system error (like the lambda failed) or if it's a user error like a code mismatch. If it's a user error, we want to return 400 status with a useful error message so it can be displayed on the frontend alert.

In this case, InvalidParameterException is returned when the email is unverified/doesn't exist. Let's return a 400 with a useful message in that case. Do the same for other user error cases.

Please look through the SDK docs and figure out ones we should look for.
See this as an example.

[jlui17]

After updating the backend to include 400 responses for user errors, please handle the 400 responses to display a useful error message to the user so they know what to do next.

See this as an example:

W2FHR/src/frontend/src/components/Authentication/helpers/authentication.ts

Lines 280 to 302 in cec8362

	switch (response.status) {
	case 200:
	const data = await response.json();
	return Promise.resolve(data);
	case 401:
	const errorText = await response.text();
	console.log("ERROR: ", errorText);
	if (errorText.includes(ERROR_MESSAGES.EMPLOYEE_NOT_CONFIRMED)) {
	return Promise.reject(ERROR_MESSAGES.EMPLOYEE_NOT_CONFIRMED);
	} else if (errorText.includes("UserNotFound")) {
	return Promise.reject(new Error("You have not registered yet."));
	} else if (errorText.includes("NotAuthorized")) {
	return Promise.reject(new Error("Incorrect email or password."));
	}
	return Promise.reject("Unknown Error");
	case 500:
	return Promise.reject(new Error("Internal server error"));
	default:
	return Promise.reject(new Error("Unknown error occurred"));
	}
	};

[jlui17]

After updating the backend to include 400 responses for user errors, please handle the 400 responses to display a useful error message to the user so they know what to do next.

See this as an example:

W2FHR/src/frontend/src/components/Authentication/helpers/authentication.ts

Lines 280 to 302 in cec8362

	switch (response.status) {
	case 200:
	const data = await response.json();
	return Promise.resolve(data);
	case 401:
	const errorText = await response.text();
	console.log("ERROR: ", errorText);
	if (errorText.includes(ERROR_MESSAGES.EMPLOYEE_NOT_CONFIRMED)) {
	return Promise.reject(ERROR_MESSAGES.EMPLOYEE_NOT_CONFIRMED);
	} else if (errorText.includes("UserNotFound")) {
	return Promise.reject(new Error("You have not registered yet."));
	} else if (errorText.includes("NotAuthorized")) {
	return Promise.reject(new Error("Incorrect email or password."));
	}
	return Promise.reject("Unknown Error");
	case 500:
	return Promise.reject(new Error("Internal server error"));
	default:
	return Promise.reject(new Error("Unknown error occurred"));
	}
	};

[jlui17]

NIT: the error message that's displayed to the client is written both on the backend and frontend. Since the error handling is kinda jank throughout our code, I won't block approval because of it. However, in the future, maybe we should consolidate all the error message to the server and just have the client display the message.

However... LGTM. GOOD WORK!!!

Let's squash merge with a message like [FEAT] move authentication to the server.

[jlui17]

LGTM