DiscoJuice in r2979
Alex Mihičinac
is something wrong with discojuice module in revision 2979? I miss some config-template files and others too (like feed.php):
# svn info
Path: .
URL: http://simplesamlphp.googlecode.com/svn/trunk/modules/discojuice
Repository Root: http://simplesamlphp.googlecode.com/svn
Repository UUID: 44740490-163a-0410-bde0-09ae8108e29a
Revision: 2979
Node Kind: directory
Schedule: normal
Last Changed Author: andreassolberg
Last Changed Rev: 2970
Last Changed Date: 2011-11-02 11:49:50 +0100 (sre, 02 nov 2011)
# find . | grep -v svn
./www
./www/favicon.png
./www/response.html
./www/central.php
./lib
./lib/CentralHelper.php
./lib/Feed.php
./lib/Country.php
./lib/EmbedHelper.php
./templates
./templates/central.tpl.php
./config-templates
./config-templates/discojuice.php
./hooks
./hooks/hook_cron.php
./hooks/hook_frontpage.php
./dictionaries
./default-disable
Best regards,
Alex
Andreas Åkre Solberg
> Hi all,
>
> is something wrong with discojuice module in revision 2979? I miss some config-template files and others too (like feed.php):
The DiscoJuice module has shrink in functionality, complexity and difficulty to setup.
The change done is towards pointing to the hosted version at discojuice.org; with a shared storage, automatic updates, translation etc.
This means that the current discojuice simplesamlphp module is just a thin layer that integrates the hosted discojuice.org version with a simplesamlphp sp.
Important feature missing is the ability to generate your own discojuicejson feeds. Instead discojuice.org provides feeds for most federations. The feed generation needed some updates anyway, so I've removed it - it may return later on in a more robust version, if requested.
The documentation is found here:
http://discojuice.org/docs/latest/guide-sp-simplesamlphp
Pretty thin - although there is not mcuh you need or should do.
I'm adding some more information about the DiscoJuice update:
> DiscoJuice 2.0
>
> I'm preparing a new release of DiscoJuice, version 2.0. This is centrally hosted version, at discojuice.org, and it should be ready today, to start playing with it. All the necessary components are available, and the documentation should be more or less up to date.
>
> https://discojuice.org/
>
> The DiscoJuice engine, is available in to two tracks, stable and dev. These will automatically point to the appropriate version of DiscoJuice. The script is minified, compressed and the hosting supports caching well.
>
> https://engine.discojuice.org/
>
> We are automatically generating feeds for most existing Identity Federations, using various techniques for getting the best data quality to feed into DiscoJuice. We support most of the MDUI extension and will make use of information in there. DiscoJuice is now multilingual, and extracts translated names of institutions from the metadata.
>
> Thanks to all of you that helped us get DiscoJuice translated into 15 different languages.
>
> Feel free to have a look at the available generated metadata feeds:
>
> https://static.discojuice.org/feeds/
>
> To get started, you probably would like to start here:
>
> http://discojuice.org/docs/latest/
>
>
> Federations on a map
>
> I plotted all the DiscoJuice prepared feeds on a map. This may be used to quality control the geo locations in metadata.
>
> http://dev.discojuice.org/map.html
>
>
> Setting up a central IdP Discovery Service for a federation
>
> DiscoJuice also contains an implementation of the IdP Discovery Protocol in javascript, and setting up a full fledged IdP Discovery Service for your federation, is now as easy as copying and pasting a static HTML page to a location of your choice; given that your federation metadata is already available as one of the prepared feeds at discojuice.org.
>
> http://discojuice.org/docs/latest/standalone
>
>
> DiscoJuice and SimpleSAMLphp
>
> There has been a discojuice module in simpleSAMLphp for quite some time, although it has never been part of a stable release. The early version has included a self-contained version of DiscoJuice. The new version now instead refers to the central hosted discojuice.org.
>
> If you earlier installed simpleSAMLphp just to get DiscoJuice working more easy, that should no longer be necessary. It should be far more easy to setup DiscoJuice now without SimpleSAMLphp.
>
> For those of you that are already using the discojuice module in simplesamlphp, you probably need to carefully consider how to proceed. Feel free to join the mailinglist for discussion the options.
>
>
> Please give feedback
>
> If things does not work as you expect it to, if you have feature requests, or if you have any questions, please use the discojuice mailinglist.
>
Alex Mihičinac
On 16. nov.2011, at 15:39, Alex Mihičinac wrote:Hi all,is something wrong with discojuice module in revision 2979? I miss some config-template files and others too (like feed.php):
The DiscoJuice module has shrink in functionality, complexity and difficulty to setup.
The change done is towards pointing to the hosted version at discojuice.org; with a shared storage, automatic updates, translation etc.
This means that the current discojuice simplesamlphp module is just a thin layer that integrates the hosted discojuice.org version with a simplesamlphp sp.
Important feature missing is the ability to generate your own discojuicejson feeds. Instead discojuice.org provides feeds for most federations. The feed generation needed some updates anyway, so I've removed it - it may return later on in a more robust version, if requested.
The documentation is found here:
DiscoJuice.org is hosting a set of automatically generated metadata feeds from the metadata of various Identity Federations.
Here you can see a list of the provided feeds here:
You may also setup your own metadata feeds.
Andreas Åkre Solberg
This means that the current discojuice simplesamlphp module is just a thin layer that integrates the hosted discojuice.org version with a simplesamlphp sp.Important feature missing is the ability to generate your own discojuicejson feeds. Instead discojuice.org provides feeds for most federations. The feed generation needed some updates anyway, so I've removed it - it may return later on in a more robust version, if requested.IMO DS is very critical element of federation, so I'm not feeling good if I do not have full control over it. Also there is hard to perform tests if testing metadata is not hosted at discojuice.org.
It would be more than welcome, to have ability to generate and include (along those hosted ones) own feeds. :-)
The documentation is found here:I've read the docs and because of article mentioned bellow I had hope, that setting up my own feed is still possible.
Alex Mihičinac
On 16. nov.2011, at 21:29, Alex Mihičinac wrote:This means that the current discojuice simplesamlphp module is just a thin layer that integrates the hosted discojuice.org version with a simplesamlphp sp.Important feature missing is the ability to generate your own discojuicejson feeds. Instead discojuice.org provides feeds for most federations. The feed generation needed some updates anyway, so I've removed it - it may return later on in a more robust version, if requested.IMO DS is very critical element of federation, so I'm not feeling good if I do not have full control over it. Also there is hard to perform tests if testing metadata is not hosted at discojuice.org.I'll be happy to add test federations.
It would be more than welcome, to have ability to generate and include (along those hosted ones) own feeds. :-)Yes, you may use the hosted 'engine', but in point to locally hosted metadata, and you can even combine and let discojuice merge.But, as you've noticed the feed generation part is not part of the module anymore. I've noticed your voice towards re-introducing this script.
The documentation is found here:I've read the docs and because of article mentioned bellow I had hope, that setting up my own feed is still possible.If interested, you may always got access to the script i run at discojuice.org. It includes several improvements over the version in the discojuice module.
Andreas Åkre Solberg
It would be more than welcome, to have ability to generate and include (along those hosted ones) own feeds. :-)Yes, you may use the hosted 'engine', but in point to locally hosted metadata, and you can even combine and let discojuice merge.But, as you've noticed the feed generation part is not part of the module anymore. I've noticed your voice towards re-introducing this script.What would be really cool is, that every federation would be able to have it's own instance of "hosted discojuice.org", so it's members would easily setup thin version of DJ.
Feed exchange then would be performed only on those hosted instances (conduct by federation operator), so setup for federation member would be even easier.
The documentation is found here:I've read the docs and because of article mentioned bellow I had hope, that setting up my own feed is still possible.If interested, you may always got access to the script i run at discojuice.org. It includes several improvements over the version in the discojuice module.Yes, please. Does that mean, I can setup my own "hosted DJ" instance? :-)
Alex Mihičinac
On 17. nov.2011, at 09:55, Alex Mihičinac wrote:It would be more than welcome, to have ability to generate and include (along those hosted ones) own feeds. :-)Yes, you may use the hosted 'engine', but in point to locally hosted metadata, and you can even combine and let discojuice merge.But, as you've noticed the feed generation part is not part of the module anymore. I've noticed your voice towards re-introducing this script.What would be really cool is, that every federation would be able to have it's own instance of "hosted discojuice.org", so it's members would easily setup thin version of DJ.Definitively a possible way to go.It turned out to be a bit complex to take all the architectural decisions on how to deploy discojuice for service providers. I'm pretty sure they would prefer a hosted solution.
The question then becomes, which federations will host a version. And what about the cross federations, such as edugain?
Feed exchange then would be performed only on those hosted instances (conduct by federation operator), so setup for federation member would be even easier.Yup.I assume service providers very soon will not need to download the whole metadata feeds anymore.1) SP will use MDX to download each entity on demand.2) SP will use discojuice that hosts and generates the disocjuice json feeds.
The documentation is found here:I've read the docs and because of article mentioned bellow I had hope, that setting up my own feed is still possible.If interested, you may always got access to the script i run at discojuice.org. It includes several improvements over the version in the discojuice module.Yes, please. Does that mean, I can setup my own "hosted DJ" instance? :-)That is definitively possible. But right now the setup is not that streamlined. I'll see if I can prepare a download link for those interested, including the neccessary components.
The work that the scripts do is:* negotiating language with user agent, gzip content, and doing conditional get for caching* prepares dictionaries files from transifex* packs all the individual files into one file, for each language, and minifies it.* keeps tracks of versions and releases of disco juice