ESI/SSO issue

Issue #2 resolved
Former user created an issue

Have all the prereqs, but cannot get past the initial login, gives me

"error: No Acess Token to verify."

on the site, and in my apache logs, it tells me

[php7:notice] [pid 5855] [client 192.168.1.3:56598] PHP Notice: Trying to get property of non-object in /var/www/html/classes/class.esisso.php on line 113

followed what you said, not sure were I went wrong...

Also, the error returned on the site has a spelling error - Access not Acess.

Comments (8)

  1. Another randomer

    I have php-curl installed and enabled. Im not the greatest with DBs, but my issue seems to be no data going to the db, but have connected to it with mysql workbench and it is online...

  2. Snitch Ashor repo owner

    The problem seems to occur before anything goes to the database. Could you try the following, open classes/class.esisso.php and replace all occurences of

    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
    

    With

    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
    
  3. Another randomer

    ok I tried that snitch, but still wouldn't pass data to the DB. I was using latest ubuntu server with preinstalled LAMP. Couldnt get it working, moved to a windows instance and works fine. not sure where the problem lies with that.

    Sorry for the delayed response and sorry I couldn't be more specific.

  4. Snitch Ashor repo owner

    coudl you edit the file classes/class.esisso.php and find this one around line 102:

    $result = curl_exec($ch);
    

    after that please add:

    print_r($result);
    die();
    

    then try to log in and send me the output please. if you do see random character strings just replace them by xxxx or whatever because there might be actual access and refresh tokens in there.

  5. Sybegh

    Read the next line on your error log, You need to change your perms on the directory.

    sudo chown -R www-data:www-data /var/www/html
    

    This will switch the perms of all directory/files to user "www-data" user which is the apache user so apache can handle the request.

    Took bout a hour to duplicate your error but this should fix it for you. Hope this helps =)

  6. Log in to comment