static.discojuice.org gets 500 response code

[Frank Tamás]

Hello,

we have been using Discojuice approx. for two month, but in the last days it has stopped to work: it does not show any identity provider in the list. I have checked the traffic generated by the discojuice.js and I saw a lot of lines like below:

GET https://static.discojuice.org/feeds/d?callback=dj_md_20 500 (Internal Server Error)

The config we use:

<script src="//ajax.googleapis.com/ajax/libs/jquery/1.6.4/jquery.min.js" type="text/javascript"></script>

<script type="text/javascript" src="https://engine.discojuice.org/discojuice-stable.min.js"></script>

<link rel="stylesheet" type="text/css" href="https://static.discojuice.org/css/discojuice.css" />

<script type="text/javascript">

    DiscoJuice.Hosted.setup(

        "a.signon", "Request Tracker",

        "https://rt.niif.hu/shibboleth",

        "https://rt.niif.hu/discojuiceDiscoveryResponse.html", ["edugain","niif"], "https://rt.niif.hu/Shibboleth.sso/DS?target=https://rt.niif.hu/rt&entityID="

    );

</script>

{…]

<a href="/rt" class="signon">Login to the RT!</a>

Thanks if you have any idea to solve this problem.

--

Tamas

[Andreas Åkre Solberg]

On 11. nov. 2011, at 11:12, Frank Tamás wrote:

Hello,

we have been using Discojuice approx. for two month, but in the last days it has stopped to work: it does not show any identity provider in the list. I have checked the traffic generated by the discojuice.js and I saw a lot of lines like below:

Ouch!

The reason why you got 500 is that https://static.discojuice.org/feeds/d?callback=dj_md_20 is not a valid URL.

It should be 

https://static.discojuice.org/feeds/edugain?callback=dj_md_20

or similar instead.

Do you have an URL of the page where DiscoJuice is deployed then I can debug more deeply.

I'll test to setup a similar environment, and report back to you if I find some major problems on my side.

Andreas

[Frank Tamás]

On 2011.11.11., at 11:32, Andreas Åkre Solberg wrote:

On 11. nov. 2011, at 11:12, Frank Tamás wrote:

Do you have an URL of the page where DiscoJuice is deployed then I can debug more deeply.

https://rt.niif.hu/

I'll test to setup a similar environment, and report back to you if I find some major problems on my side.

Thanks a lot.

--

Tamas

[Andreas Åkre Solberg]

I think I found the bug.

The reason why this was not detected during my test routines, was that I tend to use  DiscoJuice.Hosted.getConfig instead of DiscoJuice.Hosted.setup, and this specific bug did not occur with setup().

I'll fix the bug asap, and notify you when it is fixed.

Sorry about the inconvenience.

Andreas

[Andreas Åkre Solberg]

On 11. nov. 2011, at 11:41, Andreas Åkre Solberg wrote:

I think I found the bug.

The reason why this was not detected during my test routines, was that I tend to use  DiscoJuice.Hosted.getConfig instead of DiscoJuice.Hosted.setup, and this specific bug did not occur with setup().

I'll fix the bug asap, and notify you when it is fixed.

Sorry about the inconvenience.

The bug should now be fixed.

And it seems to be working at your site now as well.

Again, sorry.

Andreas

[Frank Tamás]

On 2011.11.11., at 11:51, Andreas Åkre Solberg wrote:

On 11. nov. 2011, at 11:41, Andreas Åkre Solberg wrote:

I think I found the bug.

The reason why this was not detected during my test routines, was that I tend to use  DiscoJuice.Hosted.getConfig instead of DiscoJuice.Hosted.setup, and this specific bug did not occur with setup().

I'll fix the bug asap, and notify you when it is fixed.

Sorry about the inconvenience.

The bug should now be fixed.

You were fast :) Thank you!

--

Tamas

[Andreas Åkre Solberg]

Another comment.

It seems that your SP was not authorized to get responses from the central discojuice storage. Probably because your discovery response location was not registered in the metadata export of your federations.

I've manually granted access to send responses to your SP, so now that should work.

I'd like to ask you to update the static discojuiceDiscoveryResponse.html file to the one from this location:

https://github.com/andreassolberg/DiscoJuice/blob/master/discojuice/discojuiceDiscoveryResponse.html

Then you should get rid of a unneccessary warning about no preferences being set on the central storage.

Now, you can verify that cross-domain IdP preference storage is working with your deployment of DiscoJuice, by

1) Go to http://dev.discojuice.org/demo.html - and select an IdP that also is present on your discovery service.

2) Go to https://rt.niif.hu/ - and verify that your chosen preference from (dev.discojuice...) is popped to the top of the list.

Andreas

[Frank Tamás]

On 2011.11.11., at 12:48, Andreas Åkre Solberg wrote:

I've manually granted access to send responses to your SP, so now that should work.

Thanks.

I'd like to ask you to update the static discojuiceDiscoveryResponse.html file to the one from this location:

https://github.com/andreassolberg/DiscoJuice/blob/master/discojuice/discojuiceDiscoveryResponse.html

Done.

Then you should get rid of a unneccessary warning about no preferences being set on the central storage.

Now, you can verify that cross-domain IdP preference storage is working with your deployment of DiscoJuice, by

1) Go to http://dev.discojuice.org/demo.html - and select an IdP that also is present on your discovery service.

2) Go to https://rt.niif.hu/ - and verify that your chosen preference from (dev.discojuice...) is popped to the top of the list.

It works fine, thanks.

Tamas