What steps will reproduce the problem?
1.SSO login implemented, keys generated and uploaded to Apps and Grupal
2.Registered user logs to Drupal site then
3.trying to log to Google Apps from Drupal site, on Google hosted domain
What is the expected output? What do you see instead?
Google Apps login page is expected, with already registered user (from Drupal /
grupal)
Output on site is:
Fatal error: Uncaught exception 'Exception' with message 'String could not be
parsed as XML' in /var/www/html/sites/all/modules/grupal/saml2.php:61 Stack
trace: #0 /var/www/html/sites/all/modules/grupal/saml2.php(61):
SimpleXMLElement->__construct('<?xml version="...') #1
/var/www/html/sites/all/modules/grupal/grupal.sso.inc(47):
samlResponse('joro78', 'nha.bg', '-----BEGIN CERT...', '-----BEGIN RSA ...') #2
[internal function]: grupal_single_sign_in() #3
/var/www/html/includes/menu.inc(348):
call_user_func_array('grupal_single_s...', Array) #4
/var/www/html/index.php(22): menu_execute_active_handler() #5 {main} thrown in
/var/www/html/sites/all/modules/grupal/saml2.php on line 61
SSO login not succeeded.
What version of the product are you using? On what operating system?
Drupal 6.10, Cent OS, Latest Grupal module.
Please provide any additional information below.
Trying to generate RSA keys in both ways:
#generating standart keys and certificate - standart procedure
openssl genrsa -out privateRSA.pem 1024
openssl rsa -in privateRSA.pem -pubout -out publicRSA.pem
openssl req -new -x509 -key privateRSA.pem -out cert.pem
#generating key for grupal (alternate for testing)
openssl req -new -x509 -newkey rsa:2048 -keyout grupal.key -out grupal.crt -subj '/CN=grupal/' -nodes
#renaming grupal.key and grupal.crt to grupal-key.pem and grupal-cert.pem and
uploading the letter in Google
#Apps - there .PEM file is required, tried both version of RSA key generation
# all RSA and cert files are stored at /modules/grupal root folder even the
renamed ones
Original issue reported on code.google.com by atanasov...@gmail.com on 18 Sep 2010 at 9:01
Original issue reported on code.google.com by
atanasov...@gmail.comon 18 Sep 2010 at 9:01