tiberius: Integration authentication throwing error

Hello!

I am trying out Tiberius with integrated authentication on RHEL. Connection is failing with below error

Error: Token error: ' 'Logon failed for login 'DOMAIN\USERNAME' due to trigger execution.' on server SERVERNAME executing  on line 1 (code: 17892, state: 1, class: 14)

Could someone help?

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19 (14 by maintainers)

Most upvoted comments

v0.5.9 is out with the patch.

I have cloned the repo and tried using local master branch and it worked!!

It’s easy to add of course. The thing with me and this crate is that I never want to add any public API if I’m not sure about its usefulness. SQL Server has lots of weird stuff I’m learning every day, this is one of those things…

I think that’s a good approach, TBH. Considering its lineage from Sybase, there’s 35 years of history all the way back to competing with mainframes & ISAM systems, so there are bound to be a few features that have crept in to SQL Server over time…

It’s easy to add of course. The thing with me and this crate is that I never want to add any public API if I’m not sure about its usefulness. SQL Server has lots of weird stuff I’m learning every day, this is one of those things…

Wait — @aanavaneeth , you said you were using 0.5.8? That one sets the app_name to “”.

https://github.com/prisma/tiberius/blob/923bcbf1419d414de62f8da1631a1f8efbed7401/src/tds/codec/login.rs#L148

Can you try with the master branch?

(The change to set app_name is here)

You can also from your application point to your local copy of tiberius by instead of providing a version in your Cargo.toml, set a path="/path/to/tiberius". This makes it easier for you to iterate on changes to see if you can get the authentication to work.