pds-doi-ui does not communicate to doi-service via port 8080

[gxtchen]

🐛 Describe the bug identified during I&T

document pages for confiscating pds-doi-service uses port 8080 as the default port. But pds-doi-ui use 8085 to communicate to the api server. There are no message to the doi-ui user that the port 8085 couldn't be reached unless opening the inspection tools. The use can only change the setting in pds_doi_service.ini, but no where in pds-doi-ui.
We should change the document page in pds-doi-service to use 8085.

🥼 Related Test Case(s)

🔁 : Related issues

---

➕ Additional Details

📜 To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

🕵️ Expected behavior

📚 Version of Software Used

🩺 Test Data / Additional context

🏞Screenshots

🖥 System Info

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

---

🦄 Related requirements

⚙️ Engineering Details

[jordanpadams]

@tloubrieu-jpl can you take a look at this?

@gxtchen are you saying that the documentation needs updating or you are unable to connect the DOI UI to the DOI service because of a port issue?

[jordanpadams]

@gxtchen @tloubrieu-jpl just want to follow up on this ticket. was there some email conversations to resolve this or is this still an issue?

[tloubrieu-jpl]

Hi @gxtchen sorry I missed this ticket earlier.

@jordanpadams , we already have 2 tickets which deal with that issue:

• As an administrator, I want to deploy the ui from a release and be able to change the back-end API urls #63 (configurability of the backend urls)
• As a user, I want to get an error message with support contact when the backend API is unavailable #92 (error message when backend urls are not reachable)

This is not blocking us since we can update the configuration of the back-end url then rebuild the application UI but as Gary said here, we can not currently update the backend url from the build package that Gary is testing.

We can ask Eddie to work on #63 ?

[jordanpadams]

@tloubrieu-jpl #63 is assigned to Eddie and should be next on his list.

[tloubrieu-jpl]

@eddiesarevalo @jordanpadams I am suggesting to wait for the new pds-wds-react component to be integrated before we work on this issue, see my comment on NASA-PDS/wds-react-legacy#4 (comment)

[tloubrieu-jpl]

This ticket has been solved by pds-doi-ui#63