mdq_browser problems

[fiterlinge]

The mdq_browser provided in the documentation "all in one" solution, is causing problems in its execution, it ends up not recognizing the pyff entities route, and therefore, it does not render any information, and its api is unavailable. To solve the problems, the mdq was not used, for this, the following approach was adopted:

image: docker.sunet.se/thiss-js:1.6.2 container_name: thiss ports:

• "80:80" environment:
• MDQ_URL=http://fqdn:8080/metadata/
• BASE_URL=http://fqdn/
• STORAGE_DOMAIN=domain/
• SEARCH_URL=http://fqdn:8080/role/idp.s volumes:
  • ./debug/thiss/dist:/dist

In FQDN:8080 is the functional pyff, using the generated Docker build of pyff individually. The pyff docker configuration is in the same file as thiss (docker-compose) and looks like this:

pyff: build: ../docker-pyff/. ports:

• "8080:8080" container_name: pyff-api

Returning to the context of thiss, the dist directory was mapped, so that it was possible to change (in code) the following files: thiss.js and vendors~cta~ds~index_7330c2dc291c19a00908.js. The change is related to the thiss search pattern, which was changed from "=?q" to "?query=" so that the "SEARCH_URL" route could be used. The application is functional, however it does not use MDQ, which creates complications in the process of adding new metadata to pyff (since it provides the necessary APIs). Given this context, what would be the best solution for this case? Are there more up-to-date images regarding MDQ? Are there other settings needed?

[leifj]

This is not a project that is part of theidentityselector - please report this issue on the relevant project.