1. 

   shem, Member

   We have two OEM licenses

   One is on our test server and everything works fine.
   The SSO Server URL there is set to
   https://testb.verifacto.com/vf4_shem/client/web/index.php?r=sso/index

   On my local Virtual machine it is set to
   http://localhost/vf4_shem/client/web/index.php?r=sso/index

   All the settings seem to be taken care of including $mydbr_defaults['logout']['url']

   Yet, when I login to my application and cause it to make a report request to mydbr, our SSO handler file is not being executed.
   (I have used both an IDE debugger and a file_put_contents to verify this).
   Please note: The report is indeed being retrieved. It's just not doing an SSO login first.

   Can you please help me understand why and what I need to do to fix this?
   Thanks in advance.
2. 

   myDBR Team, Key Master

   Please note: The report is indeed being retrieved. It's just not doing an SSO login first.

   So you mean the report is being run? In that case there is two possible reasons for this:

   1) The the user is already logged
   2) The report is being marked as public

   --
   myDBR Team
3. 

   shem, Member

   Yes you were correct, I was already logged in.
   I forgot about that.
   Thanks.

   p.s.
   I have put in user/defaults.php the line
   $mydbr_defaults['single_sign_on']['debug_failed_login'] = true;

   what is the purpose of that line, and and where exactly do I see any debug information?
4. 

   myDBR Team, Key Master

   The debug option is meant to be used during the development. If your SSO code is not yet working properly, it will print out debugging information when a login fails to help identifying to the

   If you have a working SSO login, you do no need that option. Nor should you use it in production environment as it will reveal sensitive information.
   --
   myDBR Team

Reply

You must log in to post.