liveuser: mapping of auth users with perm data

Hi, we intent to change the mapping of Auth User Ids to Perm User Ids to change slightly. The old idea was to do this by creating an MD5 hash of the Auth User Id and storing this both in the Auth and the Perm container. The new idea is to make it possible to use any Auth container without change. The solution to this is as following: - the mapping table in the Perm container is modified to store the Auth User ID along with the Auth source that the User Id came from Now the question is how should that datasource be stored: - should it be some dsn? - should it be an arbitrary name that must be defined in the conf file? - ... As a side note: For those people that can change their Auth container we will do the following: - there will be a service that will allow Auth containers to get a new User Id, using this the mapping process can be skipped - if you use one of the liveuser containers this will be handled for you Any comments? Anyone want to take care of this todo? Regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de