Thanks, David
I was meaning to post the below update to the forum yesterday, but inadvertently replied to Jane only instead..
Since then I have temporarily solved the auth issue by having class2go do signons, the two apps share one database, and disabling openauth from askbot (because they use a bundled dependency which is a for of django-openauth).
The two apps share session cookies.
I'll have a website using this up in about a week's time. On the auth side I would ideally like to retain an openauth signup facility, like that found on askbot, and I see from github there have been some discusions about that in the past.
______
brief status update on this (until a working version is ready shortly), and also question about authorisation..
operational:
- have got c2g and askbot running from the same server and same domain (not subdomain)
- for the moment running each of them off a different MySQL database
- c2g and askbot each have their own virtualenv (because of clashing celery version requirements)
- the two 'apps' run on two different ports and nginx routes to each one of them based on regex applied to the URL request
functional:
- askbot has a ton of features
- I have not explored its ability to limit access to forums, because for our use case we want the forums to be publicly searchable (though I believe this is doable)
- I have the forum link under a course send you to the general askbot forum with a course-tag preset (this is what they now do at udacity, they have the forum on a subdomain - it is just one big forum, and then everything is driven by a tag system, I believe - see forums.udacity.com)
users / auth:
The only unresolved issue at this stage for me is how to handle the authorisation process properly. and to integrate the concepts of users. Askbot allows for sign-on using openid (http://askbot.org/en/account/signin/?next=/en/ ) which may be advantageous depending on the use case. However, whatever the exact auth system in place, it certainly needs to be single sign on, and there are various options for implementing this. The ideal user experience is having one identity, one sign-up process, one login / logout process.
If anyone has any views on how single-sign on is best implemented in the above scenario, that would be much appreciated. I thought about setting up a seperate, third, auth server which handles all things to do with user / profile /permissions, but that might be overkill..