Issue Details (XML | Word | Printable)

Key: CORE-1922
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alexander Peshkov
Reporter: Luke Tigaris
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
Firebird Core

Trusted Authentication is not working with the Services API

Created: 04/Jun/08 01:56 PM   Updated: 19/Jan/16 04:57 AM
Component/s: Security
Affects Version/s: 2.1.0
Fix Version/s: 2.1.2

Environment: Windows XP

QA Status: No test

 Description  « Hide
The following example illustrates the problem:

gbak -r -rep c:\powerlaw\sample.fbk c:\powerlaw\sample.fdb

This restore will run just fine if trusted authentication has been enabled in the firebird server.

gbak -r -rep -se service_mgr c:\powerlaw\sample.fbk c:\powerlaw\sample.fdb

This restore will return the error "Your user name and password are not defined.". The only difference is the addition of a switch to tell gbak to run through the services manager instead of directly through native code.

gbak -se service_mgr c:\powerlaw\sample.fdb c:\powerlaw\sample.fbk

Note that this version (a backup) also works, so even though it runs through the services api!

I bring this example up because I have been working on getting existing (and working) services api code to work with new trusted authenticated mechanism. It appears only services that use the security inherit in the attach_database mechanism will work. Most service api calls will fail with bad user name and password.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Luke Tigaris added a comment - 05/Jun/08 09:37 AM
Quick work! Thanks a lot!