[Idpy-discuss] thiss-js Docker discovery service not clickable

Scott Koranda skoranda at gmail.com
Tue Sep 24 18:08:57 UTC 2019


I have a pyFF deployment answering MDQ/API queries at


I am using the master of today's thiss-js repository at commit

I did

npm intall
make docker

and it generated the image thiss-js:1.0.1

I then did

docker run \
    -d \
    --name ds \
    -e BASE_URL=http://localhost:8080 \
    -e COMPONENT_URL=http://localhost:8080/cta \
    -e PERSISTENCE_URL=http://localhost:8080/ps \
    -e MDQ_URL=https://mdq-dev.ligo.org/entities/ \
    -e SEARCH_URL=https://mdq-dev.ligo.org/api/search \
    -e LOGLEVEL=debug \
    -p 8080:80 \

To simulate an IdP discovery flow I then browsed to


The discovery page renders and I expect it would and I can type in the
text box. I see the API queries going out to the pyFF MDQ service and
the IdP I want to use is found and displayed as a choice.

When I click on the IdP choice, however, nothing happens.

The generated HTML that I am clicking on is

<a class="institution identityprovider bts-dynamic-item" tabindex="0" data-href="">
    <li><i class="arrow" data-fa-i2svg=""><svg class="svg-inline--fa fa-angle-right fa-w-8" aria-hidden="true" focusable="false" data-prefix="fa" data-icon="angle-right" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 512" data-fa-i2svg=""><path fill="currentColor" d="M224.3 273l-136 136c-9.4 9.4-24.6 9.4-33.9 0l-22.6-22.6c-9.4-9.4-9.4-24.6 0-33.9l96.4-96.4-96.4-96.4c-9.4-9.4-9.4-24.6 0-33.9L54.3 103c9.4-9.4 24.6-9.4 33.9 0l136 136c9.5 9.4 9.5 24.6.1 34z"></path></svg></i>
        <div class="d-block institution-text">
            <div class="text-truncate label primary">University of Wisconsin-Milwaukee</div>
            <div class="text-truncate label-url secondary">uwm.edu</div>

Is there some configuration I missed for running the Docker image?

I have tried both Firefox 69.0.1 and Google Chrome 77.0.3865.90 on Debian 10.

Scott K

P.S. Note that I reported yesterday an issue with pyFF MDQ not responding
correctly when the query is the sha1 hash of an entityID. Does not
being able to resolve the metadata for the SP prevent discovery from working?

More information about the Idpy-discuss mailing list