Support windows authentication for MSSQL Sever about website HOT 11 OPEN

sorry for the noob comment, but is there a way to rely on the tedious connection for this? i can connect to MSSQL using windows authentication with tedious using this connection config

var Connection = require('tedious').Connection
var config = {
  server: 'SERVER',
  authentication: {
    type: 'ntlm',
    options: {
      domain: 'DOMAIN',
      userName: 'USER',
      password: 'PASS'
    }
  },
  options: {
    encrypt: true,
    database: 'DB_NAME'
  }
}
var connection = new Connection(config)

const config = {
  host: process.env.DB_SERVER,
  dialect: 'mssql',
  dialectOptions: {
    authentication: {
      type: 'ntlm',
      options: {
        domain: process.env.DB_DOMAIN,
        userName: process.env.DB_USERNAME,
        password: process.env.DB_PASSWORD,
      },
    },
    options: {
      instanceName: process.env.DB_INSTANCE,
    }
  },
};

const sequelize = new Sequelize(
  process.env.DB_NAME,
  null,
  null,
  config,
);

As per well-hidden here, https://github.com/vishwasjois/sequelize/blob/988e754c6eef323b1a9dc11f5bee3fb535579da8/docs/upgrade-to-v5.md#dialect-specific

from website.

sorry for the noob comment, but is there a way to rely on the tedious connection for this? i can connect to MSSQL using windows authentication with tedious using this connection config

var Connection = require('tedious').Connection
var config = {
  server: 'SERVER',
  authentication: {
    type: 'ntlm',
    options: {
      domain: 'DOMAIN',
      userName: 'USER',
      password: 'PASS'
    }
  },
  options: {
    encrypt: true,
    database: 'DB_NAME'
  }
}
var connection = new Connection(config)

const config = {
  host: process.env.DB_SERVER,
  dialect: 'mssql',
  dialectOptions: {
    authentication: {
      type: 'ntlm',
      options: {
        domain: process.env.DB_DOMAIN,
        userName: process.env.DB_USERNAME,
        password: process.env.DB_PASSWORD,
      },
    },
    options: {
      instanceName: process.env.DB_INSTANCE,
    }
  },
};

const sequelize = new Sequelize(
  process.env.DB_NAME,
  null,
  null,
  config,
);

As per well-hidden here, https://github.com/vishwasjois/sequelize/blob/988e754c6eef323b1a9dc11f5bee3fb535579da8/docs/upgrade-to-v5.md#dialect-specific

You are an excellent human. I've been searching for a way to configure this for such a long time. Thank you so much!

from website.

Do you have any idea on how this could be implemented? Pull requests are welcome!

from website.

I honestly don't know how to do it. But can take a look and see how this can be done.

from website.

Anything that you can find helps! Thanks!

from website.

sorry for the noob comment, but is there a way to rely on the tedious connection for this? i can connect to MSSQL using windows authentication with tedious using this connection config

var Connection = require('tedious').Connection
var config = {
  server: 'SERVER',
  authentication: {
    type: 'ntlm',
    options: {
      domain: 'DOMAIN',
      userName: 'USER',
      password: 'PASS'
    }
  },
  options: {
    encrypt: true,
    database: 'DB_NAME'
  }
}
var connection = new Connection(config)

from website.

well-hidden indeed. Thank you!

from website.

I hoped it wouldn't be this hard to find...

So, happy to know there is a way, I will leave this open as a docs issue so that we show how to do it somewhere. Thanks everyone!

from website.

I'm pretty new to using ORMs and db drivers with node, but would I still need to use a username and password if I'm doing Windows Authentication?

I've been using msnodesqlv8 to connect with Windows Authentication through trusted_connection but I need to use a Linux environment now.

from website.

@troyfitzwater were you able to find how to use Windows Authentication (or an alternative, I do not think you can use Windows Authentication in linux) through trusted connection (not having to provide the password) in Linux?

from website.

This issue has been automatically marked as stale because it has been open for 7 days without activity. It will be closed if no further activity occurs. If this is still an issue, just leave a comment or remove the "stale" label. 🙂

from website.