Conflict between simplesamlphp_auth and drupalauth4ssp
Opened this issue · 0 comments
GoogleCodeExporter commented
If the modules 'simplesamlphp_auth' and 'drupalauth4ssp' are enabled /
activated simultaneously on the same Drupal 7 server then an empty page is
displayed. When I disable one of them or deactivate simplesamlphp_auth then it
works nicely either as an SP or and IdP. But I need both: I want to use it as a
User Register with another Drupal server (i.e. as an IdP) while I want to allow
people to register into this User Register also from external sources such as
Google and Facebook (i.e. as an SP). The User Register uses two separate
SimpleSAMLphp installations, two different MySQL databases, and different
cookies. Of course, the Google/Facebook IdP is based on a third SimpleSAMLphp
installation.
I have found out there are conflicting (redeclared) functions and classes in
'vendor/autoload.php', 'vendor/composer/autoload_real.php',
'simplesamlphp/xmlseclibs/xmlseclibs.php' and 'lib/_autoload_modules.php'.
But I have no idea what the files in the folder 'vendor' do; I have found no
clue in the documentation - is there a way to resolve these conflicts?
Original issue reported on code.google.com by peter.ha...@gmail.com on 21 Feb 2015 at 8:31