Subject | Re: Trusted Authentication working with the Services API? |
---|---|
Author | Luke Tigaris |
Post date | 2008-06-03T00:01:08Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...>
wrote:
allowed to proceed. Administrator authority should resolve to SYSDBA
but no OS user would resolve to Owner.
authority should resolve to SYSDBA". Should windows user with
Administrator rights on the local computer resolve to SYSDBA for
service api calls or not? Because, if yes, this is not working.
Please explain the purpose of the isc_spb_trusted_auth parameter if
Trusted Authentication cannot be used with the Services API. Also
what is the purpose of the undocumented string block required by
this parameter?
I was hopeful that Firebird had taken a step forward to match the
integrated security features of both MS SQL and Oracle (which have no
such limitations), but this partial implementation of trusted
authentication is very dissapointing.
wrote:
>utilities), including backup, require SYSDBA or Owner login to be
> At 06:09 AM 3/06/2008, you wrote:
>
> Many of the service calls (and the equivalent command-line
allowed to proceed. Administrator authority should resolve to SYSDBA
but no OS user would resolve to Owner.
>I do not understand what you mean when you say "Administrative
> IOW, Trusted Auth doesn't make the impossible possible.
>
> ./heLen
>
authority should resolve to SYSDBA". Should windows user with
Administrator rights on the local computer resolve to SYSDBA for
service api calls or not? Because, if yes, this is not working.
Please explain the purpose of the isc_spb_trusted_auth parameter if
Trusted Authentication cannot be used with the Services API. Also
what is the purpose of the undocumented string block required by
this parameter?
I was hopeful that Firebird had taken a step forward to match the
integrated security features of both MS SQL and Oracle (which have no
such limitations), but this partial implementation of trusted
authentication is very dissapointing.