SSO stopped working

EDIT: Could this please be moved to the support section?

I usually dislike creating new topics, especially when there's such a recent one covering a similar question. However, the issue I am encountering is a bit different.

SSO stopped working in the last 24 hours. Previous to this, we had had the system working for about 1,5 years.

The checkmarks are not all green: "moodle to joomla connectivity" is red, but it has been that way since we first installed joomdle (it has to do with our server configuration). We have not installed any new components, either on the moodle or on the joomla side.

We did change enrollment methods for one of our courses (disabled self-enrollment), but that should not be causing this error.

The normal scenario: a user coming from joomla is logged in to moodle, and sees the message that self enrollment is not possible for this course. If the user is enrolled already, he is sent to the course homepage.
What is actually happening: whether the user is enrolled or not, coming from joomla he is shown a message stating that he needs to log in to enroll into the course. After logging in he is sent to the course homepage/notified that self-enrollment is not possible.

Any ideas on where the issue might lie?

In the meantime I have gone through the installation steps for joomdle again, and have ensured that all settings and values are correct.

Hi there, sorry for the delayed response. Given this is "just" technology, something must have changed in the environment somewhere. Are you on a shared hosting environment? Did your server IP address change?

Also, you say all the values are correct yet there is a red X in the health check. As a start I would retrace back to a couple of days again to consider change that may have occurred outside of Joomla and Moodle and perhaps wit the server and network considering SSO relies on those elements too. Also, you really should address the red X to ensure proper connectivity.

Thank you for your reply, Chris.

I cannot exclude changes on the server side, as I administer the moodle and joomla administrations, but the servers are run by someone else within my organization. I will check with them on Monday and then get back to you.

The red x has been there since we first installed joomdle. I remember there was a reason why we couldn't address it, but I don't remember what it was at the moment. Will have to ask for a memory refresher on Monday as well.

Hi!

Sorry to dig up this old thread, but I haven't had much time to look into this until recently.

Regarding the red x: in the joomdle documentation the following is stated: "If Joomdle web services check is OK, you can ignore the result of this check. Sometimes it will fail due to security measures in place." Therefore, we have not looked too much into getting rid of the red x.

I have noticed something that might be helpful in reproducing the problem:
1. Log in to joomla site
2. Navigate to moodle site through joomla (SSO should work)
3. Log out using the joomla logout button
4. Navigate to the moodle site directly (yoursite.com/moodle) - to check that SSO signed me out correctly. Also, we often work on moodle content directly in moodle
5. Navigate to joomla again, and log in
6. Try to access the moodle site through joomla
7. SSO does not work

If I navigate to the joomla website from a "clean" browser (for the first time, using a private window, or after deleting cookies) the SSO works without a hitch. However, if I then log out from joomla (moodle signs me out too, as it should), visit the moodle site directly, and then try to log right back into joomla, I get the symptoms described in my opening thread.

Could there be a conflict in the cookies set by moodle when simply visiting the moodle URL, which then makes joomdle SSO break?

Which is the error in system check? If it is on the last line, you need to fix that before anything else.

"Moodle to Joomla HTTP connectivity"

Ok, that should not be a problem, if last line is fine.

Are you using redirect-less SSO? if so, can you test disabling it, to see if the problem persists?

Also, which Joomdle version are you using? I think I remember this problem, although I cannot find it in the changelog.