Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support SQL Server integrated security on *nix by enabling integrated-auth-gssapi feature in tiberius #4974

Closed
andrew-dias opened this issue Aug 8, 2024 · 1 comment

Comments

@andrew-dias
Copy link

I would like to use SQL Server's "integrated security" authentication when running Prisma on a Linux machine, but Prisma only supports this mode on Windows.

The SQL Server driver used by Prisma is https://github.com/prisma/tiberius, and this library can apparently support integrated authentication on *nix by enabling the integrated-auth-gssapi feature (see https://github.com/prisma/tiberius#integrated-authentication-trustedconnection-on-nix).

Would it be possible to enable this flag? I am guessing this would be done in quaint/Cargo.toml. Would that actually give Prisma the ability to use SQL Server integrated security from Linux?

Apologies if this request doesn't make sense, since I don't have any real Rust knowledge or real understanding of how all these projects work together in Prisma.

@jkomyno
Copy link
Contributor

jkomyno commented Jan 17, 2025

Hello, this would not only be a breaking change, but would also force us to rethink the connection mechanisms for SQL Server.

As this is not one of our high-priority databases to support, as part of our effort to clean up our GitHub repo, we’re closing this issue to help focus on features and improvements that align with our focus areas and those of our community.

For more insight into our priorities and how we’re thinking about the future of the Prisma ORM, please see our recent blog post: https://www.prisma.io/blog/prisma-orm-manifesto.

Thank you for your understanding and support!

@jkomyno jkomyno closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants