Hi Andrzej,
Thanks for reporting, it was fixed. Can you check? (rev 12039)
--
Cheers,
Dmitriy Shabanov
On Fri, 2010-07-23 at 18:30 -0400, Andrzej Jan Taramina wrote:
> Dimitry:
>
> Your realm changes have broken the Java Admin Client's ability to do a restore.
>
> Here is what happens:
>
> Restore.setAdminCredentials() calls mgmt.updateUser( dba ) which ends up calling....
>
> RemoteUserManagementService.updateUser(), which does a: parent.getClient().execute("setUser", params)
>
> which ends up calling: SecurityManagerImpl.setUser().
>
> Problem was that SecurityManagerImpl.setUser() was coded to call defaultRealm.addAccount(user), which would then throw
> an IllegalArgumentException in the RealmImpl._addAccount() method, since the admin/dba user already exists.
>
> I'm not sure why you are trying to add a new admin user rather than just setting the current user.
>
> In any case, I have hacked the SecurityManagerImpl.setUser() code and commented out the defaultRealm.addAccount(user)
> method invocation, which seems to allow the Java Admin Client to successfully initiate a Restore.
>
> Could you please look into this chain of calls, and figure out that it should really be doing, Dimitry?
>
> Thanks.
>
|
