not sure if this is the right place to discuss, but I have just had "permission" from lxbarth to move/fork the osso codebase on github across to d.o and make them contrib modules

the next step would be to upgrade them to D7

I am especially interested in making the osso provider and relying modules work nicely in Aegir, and to eventually provide some nice tools on creating site networks within Aegir (and I guess without too)

my Aegir use-case is to get common Aegir platforms (stock/pressflow, D6/D7) and distro's (stock/pressflow) Open Atrium, Open Public, Open Publish, Managing News, Drupal Commons, Open Scholar etc etc) to work together

currently I am having success with

OpenAtrium (stock) provider and D6 (stock) relying - WORKS
OpenAtrium (stock) provider and Drupal Commons 1.5 (stock) relying - FAILS

I guess we have three projects to work with

https://github.com/developmentseed/osso_provider
https://github.com/developmentseed/osso_relying

and a osso distro
https://github.com/lxbarth/osso
?

any advice or feedback welcome, this will be my first attempt, and I am basically effing hopeless

the starter question; should I create a project called osso ? would anyone else care to maintain ? (warning I am no Drupal legend)

thanks in advance

-N

Comments

niccolox’s picture

niccolox commented

the lxbarth courtesy permission
https://github.com/developmentseed/osso_relying/issues/1

alex_b’s picture

alex_b commented

This is almost an aside, but may be an important consideration:

Keep in mind that there is a very fundamental limitation when locking a site into a designated identity provider: one of the fundamental assumptions for delegated authentication is that a user is created first on the provider, then on the relying party. For instance Open Atrium breaks this assumption by using the module ucreate that allows manager users to invite new users by simply creating them right away, then sending an invite email. While this is tremendously useful for many intranet like use cases, it causes a good deal of headache when integrating OA with a designated identity provider.

niccolox’s picture

niccolox commented

thanks for the input

so, in other words, Open Atrium as an osso relying site needs ucreate turned-off ? to prevent ucreate being used to create users outside of the osso provider/relying auth ?

alex_b’s picture

alex_b commented

#3: yes, in the larger picture, plus you may want some replacement for an 'add other users' scenario if you don't want new users create their own accounts.

markwk’s picture

markwk commented

What I'm looking to do is to get Drupal 6 Provider + Modified OA as relying. I'll look at disabling U+Create and Add User in OA tomorrow.

niccolox’s picture

niccolox commented

hmm. ok..

since I have got you, have tried to install the osso provider profile, from the osso distro, within Aegir and got this error.. any ideas? 

Specified key was too long; max key length is 1000 bytes query: CREATE TABLE push_hub_subscriptions ( `timestamp` INT NOT NULL DEFAULT 0, `secret` VARCHAR(128) NOT NULL DEFAULT '', `topic` TEXT NOT NULL, `subscriber` TEXT NOT NULL, INDEX timestamp (timestamp), INDEX topic (topic(255)), INDEX topic_subscriber (topic(255), subscriber(255)) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /var/aegir/platforms/osso/includes/database.inc on line 529
niccolox’s picture

niccolox commented

my use case is pretty loose and broad.

basically I am looking at creating a site network feature in Aegir ecology .. i.e. group sites by osso provider-relying auth

my Aegir use-case is to get common Aegir platforms (stock/pressflow, D6/D7) and distro's (stock/pressflow) Open Atrium, Open Public, Open Publish, Managing News, Drupal Commons, Open Scholar etc etc) to work together

some of my Aegir Ecology crazy ideas; http://www.google.com/#sclient=psy&hl=en&source=hp&q=aegir+ecology&aq=f&...

niccolox’s picture

niccolox commented

I am not sure how I just found these chaps from Germany who have forked osso and have been working on it up until present

https://gitorious.org/~xamanu

very interestingly, they are integrating with a multi-auth Ruby app called Omniauth
https://github.com/intridea/omniauth

I will contact these folks about the contrib project

it looks like they are really the ones to take on project lead

niccolox’s picture

niccolox commented
Issue tags: +omniauth

I got the osso provider install to work by reducing the characters in the pub_hub.install


   'indexes' => array(
      'timestamp' => array('timestamp'),
      'topic' => array(array('topic', 100)),
      'topic_subscriber' => array(array('topic', 100), array('subscriber', 100)),
    ),

there is a utf8 1000 character limit (stated limitation) for MySql .....

xamanu’s picture

xamanu commented

Since drupal.org has moved to GIT. We really should use our platform form further development on that. I just opened up two sandboxes with only slightly modified modules extracted from within https://github.com/lxbarth/osso

* openid_provider_sso: http://drupal.org/sandbox/xamanu/1153574
* openid_relying_sso: http://drupal.org/sandbox/xamanu/1153576

We also have a setup running and you can easily check it out by using our drush make files:
https://gitorious.org/openid_sso/makefiles/blobs/master/osso_provider_ax...
https://gitorious.org/openid_sso/makefiles/blobs/master/osso_relying_ax....

Omniauth is actually our working title for a Drupal distribution that offers our approach of an single sign on setup. It is not related to the ruby on rails project you found on github.

niccolox’s picture

niccolox commented

correction, this is the OmniAuth Drupal distro
https://gitorious.org/omniauth

question, does it do multiple auth providers like the Ruby Rack ?

markwk’s picture

markwk commented

Looks like the relying make file was missing openid_sso that the omniauth_client profile requires. I am assuming you are referring to the dev seed version here: https://github.com/developmentseed/openid_sso.git ?

markwk’s picture

markwk commented

Ok. With openid_osso, that seems to work for the single sign on part between two D6 sites.

Sorry to be a real newbie on this topic of shared sign-in and pubsubhub, but can someone point me towards a resource or two to better conceptually follow what all this stuff is doing...?

markwk’s picture

markwk commented

I'm supposing you actually meant this one in fact: http://drupal.org/sandbox/xamanu/1153574

markwk’s picture

markwk commented

With the provider site, I'm getting the following error:
The export definition of openid_provider_sso_rps is missing the "primary key" property.

niccolox’s picture

niccolox commented

mark,

the fork of alex barth's osso is now at https://gitorious.org/openid_sso (I think) being developed by http://drupal.org/user/359937 / https://gitorious.org/~xamanu

the group working on this and related projects is https://gitorious.org/+erdfisch

I am not sure if I can give you a starting point, if you find one, let me know too !

I am out of this project for a couple of weeks while school ends...

will dive in big style for the summer

I asked xamanu if he would lead/maintain an osso project on d.o - he is really doing the work

cheers
-N

xamanu’s picture

xamanu commented

I had actually renamed openid_sso to openid_relying_sso, which has it's place here: http://drupal.org/sandbox/xamanu/1153576 I just corrected the name in omniauth_client, where the old name was still used.

Anyway we might want to stop hijacking this issue queue of openid_provider and move further discussion to the issue queues at the sandboxes:
* openid_provider_sso: http://drupal.org/sandbox/xamanu/115357
* openid_relying_sso: http://drupal.org/sandbox/xamanu/1153576

I think the osso modules will need a lot of work before they could be ready for publication. We are actually working on the whole package, but we can't make any promises about an official release anytime soon. Anyway collaboration is very welcome, if you want to help out!

niccolox’s picture

niccolox commented

agreed, will check-out the sandbox and move this conversation there.

fair enough about full release !

will give these modules a test run ASAP

really happy this approach is alive and has some momentum

cheers

-N

niccolox’s picture

niccolox commented
Status: Active » Fixed

ok, closing this ticket, tested the new sandboxed provider/relying modules and getting success

conversation continues http://drupal.org/node/1156278

thanks all for helping out

can report that the osso_provider and osso_relying sandbox modules seem to work fine (yeah!) between stock D6 sites hosted within Aegir 1.0

so, thanks felix (thanks alex barth) !!

will test this now with various combinations

i.e. D6 provider
relying Open Atrium, Drupal Commons, Open Scholar etc..

AmesEla’s picture

AmesEla commented

We you able to integrate Drupal Common with OPenPublish?

Automatically closed -- issue fixed for 2 weeks with no activity.