Hi Prabath, On Tue, Nov 17, 2009 at 3:09 AM, Prabath Siriwardena <[email protected]> wrote: > This is my requirement; > > I am going to configure an external user store with any Carbon based > products [2.0.*]. > > Now - in my external user store I have a user called 'admin' and I need > that user to login into the carbon console. > > Since - when there is a user name conflict in internal and external user > stores - we give priority to internal user store - now I want to avoid > Carbon creating a user called 'admin' in it's internal user store. > > So - before starting Carbon for the first time - I modify > conf/user-mgt.xml - following settings. > > From; > > <AdminUser> > <UserName>admin</UserName> > <Password>admin</Password> > </AdminUser> > > To > > <AdminUser> > <UserName>prabath</UserName> > <Password>prabath</Password> > </AdminUser> > > Now - my expectation is - the system won't create a user called 'admin'. > > System correctly - invalidates any authentication of 'admin' user - but > still defaultRealm.getUserStoreReader().isExistingUser(userName) > returns true - which prevents me from using 'admin' user name from my > external user store. > > Seems like we are adding the 'admin' user from a database script - > irrespective of the user-mgt.xml.
Does the database have the actual user in it after you reset the user-mgt.xml, and then erase the database followed by a restart with -Dsetup? Can you enable the H2 Web Console and verify? Thanks, Senaka. > > Any thoughts ? > > Thanks & regards. > -Prabath > > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
