Mark Rotteveel <mark@...> writes:
> > On 10-8-2013 03:54, LtColRDSChauhan wrote: > > Hi, > > 1. Connection Fails On Changing masterkey Password for > > Firebird-3.0.0.30566_0_Win32_Alpha1 with the error message : > > "Your user name and password are not defined. Ask you database > > administrator to set up a Firebird login " > > 2. Firebird provider : NETProvider-3.1.0.0. > > 3. Windows 7 32 Bit. > > 4. The connection string as under : > > <add name="conStrHIS" > > connectionString="User=SYSDBA;Password=masterkey;Database=D:\HIS\SolutionHis FBD\HISFireBird\HOSPITALINFORMATIONSYSTEM.FDB;DataSource=DBPC;Port=3050;Dial ect=3; > > Charset=NONE;Role=; Connection lifetime=15; > > Pooling=true;MinPoolSize=5;MaxPoolSize=50;Packet > > Size=8192;ServerType=Default;" > > providerName="FirebirdSql.Data.FirebirdClient" /> > > As far as I know the .NET provider does not support the new > authentication mechanism yet. The windows installer enables legacy > authentication and sets up two SYSDBA users: one with a password for the > new authentication system, and one for the old authentication system. > > However Firebird 3 alpha 1 only support one 'UserManager' at a time, and > it uses the user manager for the new authentication mechanism. So I > guess you changed the password for the SYSDBA in the new authentication > mechanism. You will probably find that you can still connect with the > old password. > > To change the password for the old authentication mechanism, you need to > edit firebird.conf and add (or update) the line UserManager = > Legacy_UserManager. > > You can then change the password with GSEC. For other ways of changing > the password you either need to restart Firebird, or do something with > gsec first. > > Jaybird also doesn't implement the authentication mechanism yet. I > described this issue on the Jaybird wiki: > http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=tip:firebird30a1 > > Mark Hi Mark, 1. Thanks for your response. 2. Did the following :- (a) Added the line UserManager = Legacy_UserManager (b) Changed the password with GSEC 3. Now the login through .NET provider works for sysdba. But the Flamerobin continues to accept the password masterkey and rejects the newly set password. Please advise. Regards, RDSC ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
