How to switch over from cURL/redirecting SSO to ....

... cURL/redirectless SSO?

[Yes, same target install: Joomla 1.7, Moodle 2.1.1, Joomdle 0.6 alpha 7, complicated internationalization redirection setup. I'm not about to propose upgrading anything until everything is working, which is mostly Moodle adjustments at this point. Joomdle has been working flawlessly in cURL/redirecting mode.]

For reference, switching the configuration does take, and removes that extra redirect that sometimes requires logging in twice to log in at all. It also completely eliminates single sign-on (the login in Joomla doesn't cross over to Moodle). I presume I have something misconfigured, but have little idea what. The Joomdle panel in Joomla looks clean, but there's something making the Moodle-side view claim "inactive" even though logins are crossing over to Moodle.

Are there any standard checklists for either:
* misconfigurations that do not affect cURL/redirecting SSO but do affect cURL/redirectless SSO?
* standard changes in configuration when changing from cURL/redirecting SSO to cURL/redirectless SSO?

Hi.

Are you running Joomla and Moodle on the same domain? That is the main requisite for it to work. I Can't think of anything else at the moment...

The intended layout site layout is: Joomla installed as web root, Moodle installed as a subdirectory of web root, e.g.

https: //www.example.com/ -- Joomla
https: //www.example.com/courses/ -- Moodle

If that's not "same domain enough" for cURL/redirectless SSO then hopefully I overlooked something in the FAQ about this.

[<b>Edit</b>: describing URLs to be typed in, above. The Moodle URL is stable, but the Joomla URL gets redirected eventually to https: //www.example.com/fr/ , which is what has to be be configured for Moodle-side to pass the health check panel]

That is the same domain, so it should work.

I don't think that the redirection should affect, but yo could try disabling it just to be sure, as I cannot think of any other problems right now.

I expect the problem that breaks cURL/redirectless SSO to be something exotic, then. Thanks.

I'll report back if I find some way to make redirectless SSO work as expected.