Fix assignment and grading CORS issues on deployment and Update user service swagger and postman

[hhchinh2002]

Pull Request

Description

• Fix assignment and grading CORS issues on deployment
• Update user service swagger and postman

Related Issue(s)

Screenshots (if applicable)

Checklist

• I have checked that the changes included in the PR are intended to merge to master or any destination branch.
• I have verified that the new changes do not break any existing functionalities, unless the new changes are intended and have approved by the team.
• I will take care of the merging and delete the side-branch after the PR is merged.

Additional Notes/References

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10444735	Triggered	Generic High Entropy Secret	85d3677	postman/user-microservice.postman_collection.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[tryyang2001]

Safe to ignore the so called "exposed" secret as long as it is just an example.