【问题标题】:how to use express-ntlm to get windows user name without authentication using NODE.js?如何使用 express-ntlm 获取 Windows 用户名而不使用 NODE.js 进行身份验证?
【发布时间】:2015-01-28 02:06:18
【问题描述】:

我正在尝试使用 express-ntlm 来获取 windows 用户名而无需身份验证。

在我的 app.js 中,我输入了以下内容:

var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'jade');

app.use(favicon());
app.use(logger('dev'));
app.use(bodyParser.json());
app.use(bodyParser.urlencoded());
app.use(cookieParser());
app.use(express.static(path.join(__dirname, 'public')));

app.use('/', routes);
var ntlm = require('express-ntlm'); 
app.use(ntlm()); 
app.use('/search', search);

加载 http://localhost:3000/search 时,node.js 中出现 401 错误 在 chrome 控制台中:无法加载资源: 加载资源失败:net::ERR_UNEXPECTED

这里的正确路由顺序是什么? 谢谢。

=========修改为==============

var express = require('express');
var path = require('path');
var favicon = require('static-favicon');
var logger = require('morgan');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser');

var routes = require('./routes/index');
var TT = require('./routes/TT');
var KYEC_stat = require('./routes/KYEC_stat');
var ftc = require('./routes/ftc');
var volPerDevice = require('./routes/topVolPerDevice');
var search = require('./routes/search');

var ntlm = require('express-ntlm'); 
var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'jade');

app.use(favicon());
app.use(logger('dev'));
app.use(bodyParser.json());
app.use(bodyParser.urlencoded());
app.use(cookieParser());
app.use(express.static(path.join(__dirname, 'public')));

app.use(ntlm()); 
app.use('/search', search);
app.use('/tt', TT);
app.use('/kyec', KYEC_stat);
app.use('/ftc', ftc);
app.use('/vol', volPerDevice);
app.use('/', routes);

/// catch 404 and forward to error handler
app.use(function(req, res, next) {
    var err = new Error('Not Found');
    err.status = 404;
    next(err);
});

======= topVolPerDevice.js ================

var config = require('../config.json');
var express = require('express');
var query = require('pg-query');
var assert = require('assert');
var async = require('async');
var url = require('url');
var queryString = require('querystring');

var router = express.Router();


/* Display quantity tested per device id since 2011 using d3 */
/* The query will first select all lot records and their earliest test date (which is the 'P' insertion incoming material quantity);
   then use {lotid, lotstartdate} to retrieve all 1st insertion lot records, then add up lots per device;
   then return the 1st 20 device id which tops inocming material quantity;
 */
router.get('/', function(req, res) {
        query.connectionParameters = config.reportConnStr;      //connecting to localhost
        var deviceArray = new Array();
        var sqlstr =  "sdfsfdfsdsfds";
        query(sqlstr, function(err, rows, result) {
            assert.equal(rows, result.rows);
            for (var i = 0; i < rows.length; i++) {
                var device = {};
                device.name = rows[i].device;
                device.value = rows[i].totalqtyout;
                deviceArray.push(device);        
            }
            res.render('d3t1', {deviceArray:deviceArray});                      
        });
});

module.exports = router;

===== 2015 年 2 月 25 日更新 =============

这周我正在重新审视这个问题,并且我已经走得更远了。 我试图在 express-ntlm.js 中写下一些调试语句,并在 firefox 中安装了 firebug。事实证明,这可能与中间件的顺序无关。

return function(request, response, next) {
    if (!request.connection.id) {
        request.connection.id = utils.uuidv4();
    }

    var auth_headers = request.headers.authorization;

    var user = request.connection.ntlm;
....
}

在这里,我的 request.connection.ntlm 为空。

这可能是什么原因?是关于浏览器设置还是我的网络设置?

我在公司网络上运行它,并且我在网络域中。

【问题讨论】:

  • 原始问题的更新。
  • 其实request.connection.ntlm为空也没问题。这是为了检查连接是否已经过身份验证。
  • 你能试试这个基本设置吗? var express = require('express'), ntlm = require('express-ntlm'); var app = express(); app.use(ntlm()); app.all('*', function(request, response) { response.end(JSON.stringify(request.ntlm)); }); app.listen(80);
  • 嗨@Fabio,我试过了。它不会到达 app.all() 部分。
  • 代码会执行到handle_type1(...) => connect_to_proxy(...) => proxy.negotiate(...) 然后去connect_to_proxy(...)的回调,它只是将状态码设置为 401 并结束响应。这是在某个地方发出故障信号吗?

标签: javascript node.js express express-ntlm


【解决方案1】:

更新:

在 app.js 中改成这个:

app.use(ntlm()); 
app.use('/', search);
app.use('/', TT);
app.use('/', KYEC_stat);
app.use('/', ftc);
app.use('/', volPerDevice);
app.use('/', routes);

并在路由器的topVolPerDevice文件中添加'/vol':

var config = require('../config.json');
var express = require('express');
var query = require('pg-query');
var assert = require('assert');
var async = require('async');
var url = require('url');
var queryString = require('querystring');

var router = express.Router();


/* Display quantity tested per device id since 2011 using d3 */
/* The query will first select all lot records and their earliest test date (which is the 'P' insertion incoming material quantity);
   then use {lotid, lotstartdate} to retrieve all 1st insertion lot records, then add up lots per device;
   then return the 1st 20 device id which tops inocming material quantity;
 */
router.get('/vol', function(req, res) {
        query.connectionParameters = config.reportConnStr;      //connecting to localhost
        var deviceArray = new Array();
        var sqlstr =  "sdfsfdfsdsfds";
        query(sqlstr, function(err, rows, result) {
            assert.equal(rows, result.rows);
            for (var i = 0; i < rows.length; i++) {
                var device = {};
                device.name = rows[i].device;
                device.value = rows[i].totalqtyout;
                deviceArray.push(device);        
            }
            res.render('d3t1', {deviceArray:deviceArray});                      
        });
});

module.exports = router;

【讨论】:

  • 谢谢 MrBearAndBeer。我用推荐的编辑重新发布了我的问题,但是,它仍然显示 GET /search 401 5ms 有什么想法吗?
  • 你能告诉我一个路由文件的代码吗?
  • 再次感谢 MrBearAndBeer。我重新发布了我的路线 JavaScript。
  • @sqr 你能把所有的应用分享到 github 或者发到我的邮箱吗?
  • @sqr 查看我的更新答案.. 我尝试更新问题而不是我的答案,对不起..
猜你喜欢
  • 1970-01-01
  • 2016-03-24
  • 2018-04-29
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 2012-01-13
  • 2016-08-15
  • 2017-02-18
相关资源
最近更新 更多