Versions Compared

Old Version 29

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 30

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  • 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, 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.server.url configuration, as they are the default ports for HTTP and HTTPS respectively.
  • 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 logins coming from the frontend.