-
Notifications
You must be signed in to change notification settings - Fork 9
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
Pluggable sspi-client #41
base: master
Are you sure you want to change the base?
Conversation
native.js contains changes made by @arthurschreiber that make sspi-client pluggable
Heya @v-suhame 👋, I'm really sorry I did not get to this sooner! 😞 What do you think about actually keeping the authentication provider for tedious and the The way Whatever you decide here, I'll also leave a separate review for the code as it is proposed in this pull request. 😄 Also, on an unrelated note, I remember you suggested transferring |
// what to do if the module is not supported on the platform where it's running. | ||
if (require('semver').gte(process.version, '4.0.0') && os.type() === 'Windows_NT') { | ||
module.exports.ModuleSupported = true; | ||
const NativeAuthProvider = require('./native.js').NativeAuthProvider; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about removing the .js
extension from the paths passed to the require
calls?
// in applications like Tedious which supports older version of node.js, even | ||
// if the functionality itself won't be available. The application can decide | ||
// what to do if the module is not supported on the platform where it's running. | ||
if (require('semver').gte(process.version, '4.0.0') && os.type() === 'Windows_NT') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about putting the version requirement for Node.js into the package.json
file, and removing it from here? That'd allow you to get rid of the semver
dependency as well.
@@ -0,0 +1,78 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about removing this whitespace here?
👍 I'm thinking of doing the same for @tvrprasad can you transfer |
If you can share the steps on how I may do that, I'll be happy to do that. Is there some permission I have that you don't that makes it necessary that I do it? If you're able to do it, please go for it. You have my permission :-) |
I don't have the permission to transfer. You can refer https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/#transferring-a-repository-to-another-user-account-or-to-an-organization |
@v-suhame I got an error saying I don't have permission to create a repository under tediousjs. Can you give me permission so I can complete the transfer? |
I don't have that access either 😅 |
@arthurschreiber Can you just fork sspi-client and transfer to tediousjs? Or you can give me temporary permission to create a repository under tediousjs and I'll do the transfer. |
Refactored sspi-client to go in hand with tediousjs/tedious#624 (native.js was moved from there)
To use windows integrated auth in tedious, the connection would be,
@arthurschreiber Can you have a look at this?
TODO
negotiate
as default security package, if undefined