我尝试使用 PEP Wilma 6.2 保护猎户座。虽然 PEP 代理启动,但它无法获得“x-subject-token”。为什么PEP不能得到它?我的配置是否不正确或不足?
PEP Proxy Wilma 6.2
server.js:70
IDM.authenticate (function (token) {
log.info('Success authenticating PEP proxy. Proxy Auth-token: ', token);
}, function (status, e) {
lib/idm.js:22
var authenticate = function(callback, callbackError) {
var options = {
host: config.idm.host,
port: config.idm.port,
path: '/v3/auth/tokens',
method: 'POST',
headers: {'Content-Type': 'application/json'}
};
.............................................
log.info(options); // debug
log.info(protocol); // debug
log.info(body.auth.identity.password.user); //debug
proxy.sendData(protocol, options, JSON.stringify(body), undefined, function (status, resp, headers) {
my_token = headers['x-subject-token'];
log.info("my_token:", my_token); //debug
callback(my_token);
}, callbackError);
日志:'my_token' 是不受约束的。
pep | 2018-04-12 10:27:44.665 - INFO: Server - Starting PEP proxy in port 80. IdM authentication ...
pep | 2018-04-12 10:27:44.667 - INFO: IDM-Client - { host: 'account.lab.fiware.org',
pep | port: 5000,
pep | path: '/v3/auth/tokens',
pep | method: 'POST',
pep | headers: { 'Content-Type': 'application/json' } }
pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client - http
pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client - { name: 'pep_proxy_132e42370ad546a8b85d21dd7453b4ae',
pep | password: '9077ddf99863487296a75f1ef8fef297' }
pep | 2018-04-12 10:27:45.723 - INFO: IDM-Client - my_token: undefined
pep | 2018-04-12 10:27:45.723 - INFO: Server - Success authenticating PEP proxy. Proxy Auth-token: undefined
先感谢您。
我在 4 月 25 日在日志下方添加
pep | 2018-04-25 11:58:26.229 - INFO: Server - Starting PEP proxy in port 80. IdM authentication . ..
pep | { host: 'account.lab.fiware.org',
pep | port: 5000,
pep | path: '/v3/auth/tokens',
pep | method: 'POST',
pep | headers: { 'Content-Type': 'application/json' } }
pep | http
pep | { name: 'pep_proxy_5e45c606882c469aa6413e9993e040**',
pep | password: '9c01e49e55434b40a6436aeb61095c**' }
pep | *** response ***
pep | status: 0
pep | resp: Error: connect ECONNREFUSED
pep | at errnoException (net.js:905:11)
pep | at Object.afterConnect [as oncomplete] (net.js:896:19)
pep | headers: { '': undefined }
pep | my_token: undefined
pep | 2018-04-25 11:58:27.301 - INFO: Server - Success authenticating PEP proxy. Proxy Auth-token: undefined