|
I'm trying to implement single-sign-on to OSQA from a portal system (DotNetNuke) with an existing user base. So far, I found django-sso as a potential solution ( http://code.google.com/p/django-sso/ ) and http://stackoverflow.com/questions/4662348/implementing-single-sign-on-sso-using-django - but as I'm neither a Python nor Django developer I might some more steps on how to set this up. In particular, assuming that django-sso is the simplest solution, how would the links look for authentication? |
|
You may have bitten off more than you intended to, since the OSQA user object is not 100% django. There are things that go on during the creation, management and caching of OSQA users that are not handled by django at all. If you're simply looking to offload your user authentication to a different database or user directory, then you nay want to use a custom OSQA plugin to achieve this. DZone has writeen many of these for customers, and we'd be happy to have you select us to work on yours. Actually, what I need to do is have a link in the portal system to OSQA that the user can click. The link would contain some sort of "session ID" that would be passed to OSQA. Then OSQA needs to check back with the portal system whether that "session ID" is still valid and does indeed represent the given user (OSQA and portal system are hosted on the same machine, so that would be "local communications" ;-) ). Once that check is passed, if the user doesn't exist in OSQA, it has to be created and logged in. If it already exists, it just needs to log in.
(20 Aug '11, 07:50)
jashan
jashan the comment you wrote is that just I try to do. Have you found a solution for that?
(14 Sep '11, 09:56)
samet
Not yet, sorry ... but I'll eventually look deeper into that (I've been busy with other things for a while).
(16 Sep '11, 12:20)
jashan
|
