Versions Compared

Key

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

...

  • Review commons installation issues (LINK COMING)
  • Ask for Support via one of the support options documented on that page

Common Installation Issues

Frontend is throwing a 403 error every time I try to login

If you are seeing a 403 Forbidden error every time you try to login (with a known, valid password), then it's likely you have a configuration issue which is blocking the frontend from accessing the backend.

  • Verify that the URLs in your Frontend's src/environments/environment.common.ts  EXACTLY MATCH the Backend's local.cfg 
    • Backend's dspace.ui.url MUST reference the same URL as the Frontend's "ui" configuration section.  Modes (http vs https), ports, hostnames AND nameSpace (or path) must all match.
      • Keep in mind if you are using port 80 or port 443, those can be left off the dspace.ui.url configuration, as they are the default ports for HTTP and HTTPS respectively.
    • Backend's dspace.server.url MUST reference the same URL as the Frontend's "rest" configuration section.  Modes (http vs https), ports and hostnames must all match.
      • Keep in mind if you are using port 80 or port 443, those can be left off the dspace.server.url configuration, as they are the default ports for HTTP and HTTPS respectively.
      • Also keep in mind that the "dspace.server.url" configuration should NOT include the "/api" path, whereas the "rest" configuration section MUST include that path (as "/api" is the location of the REST API within the server webapp).
  • If the above all match, you can also double check the CORS (Cross-origin resource sharing) configuration on the Backend to ensure that it includes the Frontend's URL
    • rest.cors.allowed-origins specifies the client URLs which are allowed login access to the Backend. It MUST include the Frontend URL (though by default it does) or else the backend will block all access to the frontend.