On Thu, May 23, 2013 at 12:13 AM, Pushpalanka Jayawardhana <[email protected]>wrote:
> Hi All, > > Here is a status update of the feature implementation. Looking for advice > on few areas too. > > [image: Inline image 2] >> >> *Done* > > - Detect dropping of new user-mgt.xml and create new > realmConfiguration from the file (Using Axis2 deployer. As I have observed > this detects the dropping of a new a file, but not the editing of an > already existing file. Please correct me if I am wrong.) > > You need to switch on the hotupdate. This can be done in axis2.xml. > > - > - UI to show the existing configuration and edit the properties of > UserStoreManager > > > *Working on > * > > - Making the newly created realmConfiguration effective through the > RealmService (Need to address changing primary user store, already signed > in users in the current configuration, secondary user stores) > > I think what we discussed was to add only secondary user stores though UI. Primary user store need to configure from the user-mgt.xml file and that should support multitanancy. When a tenant is created, tennat super users details are stored in primary user store. If the tenant Admin need to add other user stores he can add them through UI. > > > > - In the UI, the details of the available > UserStoreManagers(Implementation class and properties list) needs to be > shown. In order have them, I am to introduce UserStoreRegistry with a > ServiceTracker in carbon.user.core. It will have same functionality as > AuthenticatorsRegistry, but for UserStoreManagers. Objective is to make > sure that, if a user drops a custom UserStoreManager in addition to the > existing ones, UI should detect it and allow user to utilize it via UI. > > We need to see the UI to comment on this. > > > > - Saving data inserted via UI, at finish - This has few options. > Please advice on best to use > - Update the RealmService with new configuration and then write the > updated Realmconfiguration into user-mgt.xml (This newly created file > will > trigger the Axis2 deployer as a new file addition, which is not needed ) > - Write the updated details into user-mgt.xml. Even if only one > UserStoreManager is edited, whole user-mgt.xml has to be read in, place > new > one in relevant order and update other's order accordingly. > > Idea is to create a separate file per user store. you can save this file with the userstore name. Then update only that file. thanks, Amila. > > - > > > > Thanks, > > Pushpalanka Jayawardhana > > Software Engineer > > WSO2 Lanka (pvt) Ltd > [image: > Facebook]<http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.facebook.com%2Fpushpalanka> > [image: > Twitter]<http://s.wisestamp.com/links?url=http%3A%2F%2Ftwitter.com%2FPushpalanka> > [image: > LinkedIn]<http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.linkedin.com%2Fprofile%2Fview%3Fid%3D75175642%26trk%3Dtab_pro> > [image: > Blogger]<http://s.wisestamp.com/links?url=http%3A%2F%2Fpushpalankajaya.blogspot.com%2F> > [image: > SlideShare]<http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.slideshare.net%2FPushpalanka> > Mobile: +94779716248 > <http://s.wisestamp.com/links?url=http%3A%2F%2Fr1.wisestamp.com%2Fr%2Flanding%3Fu%3Dc984892c0c4ca423%26v%3D3.13.2%26t%3D1361257731639%26promo%3D10%26dest%3Dhttp%253A%252F%252Fwww.wisestamp.com%252Femail-install%253Futm_source%253Dextension%2526utm_medium%253Demail%2526utm_campaign%253Dpromo_10> > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805
<<revised2.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
