Task:Single sign-on/Status - Revision history

imported_>amigadave: categorize

2010-05-11T08:38:58Z

categorize

← Older revision		Revision as of 08:38, 11 May 2010
Line 120:		Line 120:
	*** Web UI for user		*** Web UI for user
	*** REST API for applications		*** REST API for applications

			[[Category:Tasks]]

imported_>amigadave: wikify links

2010-04-13T13:36:55Z

wikify links

← Older revision		Revision as of 13:36, 13 April 2010
Line 9:		Line 9:
	*All editing interfaces should redirect to Midgard n.n.account		*All editing interfaces should redirect to Midgard n.n.account
	**Registration also happens there		**Registration also happens there
	*Niels has [~~http://wiki.maemo.org/~~Task:Single_sign-on/Account_info_stored_in_ldap documented] what data we need to manage		*Niels has [[Task:Single_sign-on/Account_info_stored_in_ldap\|documented]] what data we need to manage
	**Add to the n.n.accounts DM2 schema		**Add to the n.n.accounts DM2 schema
	*When user is edited in Midgard we should push the data to backend		*When user is edited in Midgard we should push the data to backend
Line 58:		Line 58:

	==== Keep informed ====		==== Keep informed ====
	Here, in the monthly [~~http://wiki.maemo.org/~~Maemo.org_Sprints/May_09 sprints] and on my [http://danielwilms.wordpress.com blog] you can get always the newest information on the topic. In a couple of weeks we will meet again to discuss the status. I hope there will be a lively discussion in the meanwhile to get new ideas, comments and suggestions.		Here, in the monthly [[Maemo.org_Sprints/May_09\|sprints]] and on my [http://danielwilms.wordpress.com blog] you can get always the newest information on the topic. In a couple of weeks we will meet again to discuss the status. I hope there will be a lively discussion in the meanwhile to get new ideas, comments and suggestions.

	== Test environment setup ==		== Test environment setup ==

imported_>danielwilms at 11:33, 23 July 2009

2009-07-23T11:33:41Z

← Older revision		Revision as of 11:33, 23 July 2009
Line 1:		Line 1:
	This wiki page should give an update of the current status of the SSO implementation for the maemo.org components. The concept behind it and the reasons for the chosen implementation can be found here: [[Task:Single_sign-on]]		This wiki page should give an update of the current status of the SSO implementation for the maemo.org components. The concept behind it and the reasons for the chosen implementation can be found here: [[Task:Single_sign-on]]

			== SSO Status meeting 23-07 ==

			'''Wiki is fully integrated'''
			* sign-in and sign-out

			'''User information'''
			*All editing interfaces should redirect to Midgard n.n.account
			**Registration also happens there
			*Niels has [http://wiki.maemo.org/Task:Single_sign-on/Account_info_stored_in_ldap documented] what data we need to manage
			**Add to the n.n.accounts DM2 schema
			*When user is edited in Midgard we should push the data to backend
			**which will notify other services
			**done as MidCOM watcher in the org.maemo.cas component

			'''User information exchange'''
			*Web services on top of Midgard MVC (midgard2)
			*PULL interface that services can poll
			**Changes since transaction ID XX
			*PUSH interface for notifying services about changes
			**webhooks http://blog.webhooks.org/about/
			*Implementation
			**Additional software (on the same server as CAS?)
			***midgard2
			***mysql (for userdata storage)
			**Midgard MVC component for providing the web services
			***JSON as transfer medium
			***SSL client cert authentication between services and the Midgard2 instance
			**CAS talks directly to MySQL
			***CAS needs just username and password in some table (encryption?)
			**The protocol specification needed ASAP (Alexey)
			***Look up similar implementations in other web services


	== Discuss it! ==		== Discuss it! ==

imported_>danielwilms: /* Test environment setup */

2009-07-07T12:34:33Z

Test environment setup

← Older revision		Revision as of 12:34, 7 July 2009
Line 48:		Line 48:
	* CAS authentication integrated		* CAS authentication integrated
	* User can log in and logout using CAS		* User can log in and logout using CAS
			* Single sign-out now working


Line 60:		Line 61:
	* Applications could request data from it		* Applications could request data from it
	* Right now just a UI as a user registry		* Right now just a UI as a user registry


	== Issues ==		== Issues ==

imported_>danielwilms: /* Issues */

2009-07-07T12:33:27Z

Issues

← Older revision		Revision as of 12:33, 7 July 2009
Line 64:		Line 64:
	== Issues ==		== Issues ==

	* ISSUE: Wiki: no anonymous reading allowed right now
	* ISSUE: LDAP/registry not over secure connection		* ISSUE: LDAP/registry not over secure connection
	* ISSUE: Single sign out not implemented yet for wiki


	== Next steps ==		== Next steps ==

imported_>danielwilms: /* Discuss it! */

2009-05-28T07:43:47Z

Discuss it!

@@ Line 3: / Line 3: @@
 == Discuss it! ==
-If you have suggestions, ideas, comments or questions feel free to join #maemo-meeting, 27.05. 12:00 UTC
+If you have suggestions, ideas, comments or questions feel free to join [http://maemo.org/maemo-meeting/sso-meeting-2009-05-27.html #maemo-meeting, 27.05. 12:00 UTC]
 == Test environment setup ==

imported_>danielwilms: moved

2009-05-27T14:43:07Z

moved

New page

This wiki page should give an update of the current status of the SSO implementation for the maemo.org components. The concept behind it and the reasons for the chosen implementation can be found here: [[Task:Single_sign-on]]

== Discuss it! ==

If you have suggestions, ideas, comments or questions feel free to join #maemo-meeting, 27.05. 12:00 UTC

== Test environment setup ==

Here you find the current status of the test environment. It is not meant for testing, but it should inform about the status right now.

[[Image:Architecture_test_envi.jpg]]

'''Authentication Server'''

* Instance of CAS running on the test server
* Apache Tomcat used as servlet container
* Secure connection
* self signed certificate used for testing purposes
* LDAP directory used for user authentication (running on virtual machine)

'''Mediawiki'''

* Instance of mediawiki running on the test server
* Apache web server used to host the wiki
* CAS authentication integrated
* User can log in and logout using CAS

'''GForge'''
* Instance hosted by apache web server running in test environment
* Integration ongoing

'''User Management System'''
* Abstracted of the others components
* Should contain all the user related data
* Applications could request data from it
* Right now just a UI as a user registry

== Issues ==

* ISSUE: Wiki: no anonymous reading allowed right now
* ISSUE: LDAP/registry not over secure connection
* ISSUE: Single sign out not implemented yet for wiki

== Next steps ==

* Full integration of GForge
* Concept user data management -> apart from CAS
** Merging of different userdatabases (bugzilla, talk, midgard)
* Midgard integration
* Getting Wiki, Midgard, GForge in a shape for public testing

== Future Plans ==
* integration of bugzilla, talk

== Open Questions ==
* How should the application get the data from the user management system
** First possibility:
*** Just UI to register user and update data
*** Other components get data by LDAP-access
** Second idea:
*** Web UI for user
*** REST API for applications