Repository navigation
Federated authentication in development environment
You have turn the frontend up before the backend
By adding this, every time you type tts-dev.niaefeup.pt on the browser, it will redirect to the localhost in order for us to access the localhost container that way.
Add the following line to the /etc/hosts file:
127.0.0.1 tts-dev.niaefeup.ptAdd the following line to the /etc/hosts file:
127.0.0.1 tts-dev.niaefeup.ptFollow this guide.
In order to use federated authentication we need to have a valid Fully Qualified Domain Name and we need to support HTTPS.
In order to support HTTPS, we need to have a certificate in the backend.
That certificate needs to be signed by a Certificate Authority (CA). Due to this, we have to add a new CA to the browser.
The certificate files are available in the NIAEFEUP Google Drive Folder.
This is the rootCA.crt file.
-
Access the security settings by typing
chrome://settings/securityto the url. -
Click on
Manage certificates -
Import the certificate using the
rootCA.crtfile.
This is the server.key file, which is the private key for the certificate. The certificate is already set inside the nginx folder in the backend.
Add the server.key file to the nginx/cert folder on the backend.

The
SIGARRA_USERNAMEis the mecanographical number not including up (for example,202112345instead ofup202112345)

Ask the project coordinator or someone that has these credentials
Change the VITE_APP_BACKEND_URL to https://tts-dev.niaefeup.pt/api in the .env file on the frontend.
Currently, the frontend must be already running when the turning on the backend.