The registration and evacuee facing portal
- Configure the following as secrets of
EMBC.Registrants.API
:
{
"auth": {
"introspection": {
"authority": "[oauth server url in OpenShift or local]",
"clientid": "[API client id as configured in oauth server configuration]",
"clientsecret": "[API client secrets as configured in oauth server configuration]"
},
"jwt": {
"authority": "[oauth server url in OpenShift or local]"
},
"oidc": {
"issuer": "[oauth server url in OpenShift or local]",
"clientid": "[UI client id as configured in oauth server configuration]"
}
},
"messaging": {
"authorizationEnabled": "true",
"oauth": {
"metadataAddress": "[oauth server url in OpenShift or local]/.well-known/openid-configuration",
"clientId": "[API client id as configured in oauth server configuration]",
"clientSecret": "[API client secrets as configured in oauth server configuration]",
"scope": "ess-backend"
}
},
"captcha": {
"automation": "[optional automation captcha value as configured in the automation test suite]"
}
}
- to run the API locally, run the following projects:
/ess/src/API/EMBC.ESS.Host/EMBC.ESS.Host.csproj
/registrants/src/API/EMBC.Registrants.API/EMBC.Registrants.API.csproj
- in
registrants/src/UI/embc-registrant
, run
npm install --ignore-scripts
- to run the UI with a local API, run
npm start
- to run the UI and use the a remote dev environment API, without the needs to run the API locally (step 2), run
npm run start-prj
npm run start-sup
- to auto generate the API client side code, run the one of the following (depends on which environment has the API changes):
npm run gen-api-local
npm run gen-api-prj
npm run gen-api-sup
- before committing UI code changes, run the following to ensure the code will pass linting:
npm run format:write
npm run lint -- --fix
- before committing API code changes, run the unit tests to validate mapping and ensure all tests are green