Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This service requires an IDIR account. You can open this link https://getok.nrsapi.gov.bc.ca/devportal/api-directory/3181?preview=false and https://api.gov.bc.ca/devportal/app/requestAccountapi-directory/3182?preview=false to request an account after logging in with your IDIR. This will provide you with an API client id and secret to the CHES and CDOGS service.

...

Accessing CHEFS from an external network may result in a forbidden access 403 Error. To fix this, navigate to the Keycloak login page at http://localhost:8082/ and log in with the username and password “admin” after you have completed the build process. Under Configure > Clients, for both chefs and chefs-backendfrontend, add an asterisk * to the Web Origins field. This will permit all CORS origins and should solve the 403 Forbidden Error.

If you are hosting keycloak on an openshift server, ensure that in your `chefs-server-config` that your server_kc_publickey matches the value found in your keycloak server. You can obtain that value by going to your realm settings, clicking on keys, then clicking on the public key button for RS256.

...

...

Using Test Installation JSON

...

If your system cannot run on the default port http://localhost:8081/, navigate to the Keycloak login page at http://localhost:8082/ and log in with the username and password “admin” after you have completed the build process. Under Configure > Clients, for both chefs and chefs-backendfrontend, add your URI under the Valid Redirect URIs field.

...