Is there any chance the project is willing to implement or take in patches which will implement cross domain authentication?
Or is this something that strongly goes against the project's roadmap/philosophy.
I believe this is one of the most seamless SSO modules I've tried so far requiring no other third parties, with the only limitation being cross domain support.
N/A
Provide cross domain authentication support, where if it detects that a slave site is on a different domain, it does it a redirect with a special bakeryAuthToken GET parameter which contains encoded hmac data which can then be decoded and used to authenticate (and set the appropriate cookies and login).
It can also be behind a configuration flag if this is a feature that needs to be opted in for.
Provide issue fork/patch.
N/A.
Includes API and methods to facilitate cross domain authentication.
N/A.
Active
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This module is for sites that are on the same second-level domain. It would not work for other cases, and making it work for those case is out-of-scope for this module.
If you need SSO for sites that are not on the same second-level domain, there are other modules that work in that case.