Wed 29 Jul 2009 |
| JConnect - Release Candidate 1 |
| Written by Arunoda Susiripala |
No more Fetures >>I've implemented all the features we were expected to do and implented some other feature which are not decided at the first such as Single Sign On. More details about JConnect features can be found here. How it worksin this I would like to tell you some of the features(internals) and how they've implements. for this time I would like to express about authentication and single sign On from External Applications.
Single Sign On and AuthenticationTo implement Sign Sign On and Authentication into JConnect was hard for me. Because although I choosed to integrate Elgg ; JConnect should be designed in a more generalised way and could be able to use with any application.
So at first I choosed an OpenID framework to do that. by using that I convert Joomla into a OpenID identity povider and Elgg becomes and OpenID client. It works. and sometimes it fails on some servers and it takes a lot of process time. Then I realized that OpenID is not the best solution for this and it does some processes that are meaning less for JConnect. So I read about how openID works and built a customized and minized version of OpenID that will work fine for JConnect. here's the flow diagram of that Process.
OK! That's authentication where's the Single Sign On ?
See it for user-self
Download and other infomationhttp://jconnect.googlecode.com Feedbacks and NextI would really like to here feedbacks from you and if there's issue I really like to here about that. anyway in the next blog posts I would like to show about some other internals and Developer version of JConnect. thank you! |
