Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

403 Error

Accessing CHEFS externally may result in a 403 Forbidden Error. To fix this, navigate to the Keycloak login page at http://localhost:8082/ once you have completed the build process. Under Configure > Clients, for both chefs and chefs-backend, add an asterisk * to the Web Origins field. This will permit all CORS origins and should solve the 403 Forbidden Error.


Common Services API Access

This service requires an IDIR account. You can open this link https://getok.nrs.gov.bc.ca/app/requestAccount 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.

It’s not necessary to immediately obtain access to CHES and CDOGS. If you wanted to take advantage of the document generator and email service in the future then this is where you would do it.


Cannot connect to the Docker daemon:

Before running docker compose up, you will need to start the Docker daemon. Most Linux distributions use systemctl to start services and the macOS equivalent is launchctl. Use the following command to run the Docker daemon:

sudo systemctl start docker

or

sudo launchctl start docker

for Mac users.

If you are using the Docker desktop app, starting the application and then running docker compose up will also work.


App not loading on localhost

After running npm run serve, the App should be running at http://localhost:8081/app/, but if you have issues where it is not loading, try the following:

  1. Disable checkLoginIFrame

    Edit the loadKeycloack(config) function in /common-hosted-form-service/app/frontend/src/main.js to look like:

    function loadKeycloak(config) {
      Vue.use(VueKeycloakJs, {
        init: { onLoad: 'check-sso', checkLoginIframe: false },
        config: {
          clientId: config.keycloak.clientId,
          realm: config.keycloak.realm,
          url: config.keycloak.serverUrl
        },
        onReady: () => {
          initializeApp(true, config.basePath);
        },
        onInitError: error => {
          console.error('Keycloak failed to initialize'); // eslint-disable-line no-console
          console.error(error); // eslint-disable-line no-console
        }
      });
    }

setting the checkLoginIframevalue to false.

Before pushing your code, remember to revert the changes to main.js, removing the checkLoginIFrame variable from the code.

2. CORS Unblock Extension

In case you get an error message where access is blocked by CORS policy similar to the one below:

Download the CORS Unblock extension for chrome and enable the following settings:

This extension disables CORS security and should allow you to load the local instance of your application.

  • No labels