InternalOpenIDError: Failed to verify assertion
at /var/nodejs/Website/node_modules/passport-openid/lib/passport-openid/strategy.js:184:36
at /var/nodejs/Website/node_modules/openid/openid.js:927:12
at /var/nodejs/Website/node_modules/openid/openid.js:1051:16
at /var/nodejs/Website/node_modules/openid/openid.js:1169:16
at Request._callback (/var/nodejs/Website/node_modules/openid/openid.js:190:7)
at Request.self.callback (/var/nodejs/Website/node_modules/request/request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (/var/nodejs/Website/node_modules/request/request.js:1035:10)
at emitOne (events.js:82:20)
GET /auth/steam/callback?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Flogin&openid.claimed_id=http%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198197967283&openid.identity=http%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198197967283&openid.return_to=http%3A%2F%2Fcsgomayhem.com%2Fauth%2Fsteam%2Fcallback&openid.response_nonce=2015-11-25T18%3A40%3A44ZOdgvGQXoVnz9LWfko54I371tMOM%3D&openid.assoc_handle=1234567890&openid.signed=signed%2Cop_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle&openid.sig=L5jXiwo2S4mVe0r%2BkcpU%2Bj%2BaEEU%3D 500 665ms - 708b
I've had my code working for several weeks now in my windows dev environment but now trying to run it on an Ubuntu 14.04 prod machine I am presented with this error when authenticating someone through Steam. I have no idea what the error means and Googling and searching on here hasn't yielded any results. I can provide the relevant code if you tell me what I'm looking for or if this is an easy fix please let me know.
All help would be greatly appreciated, regards.
I solved this by downgrading my version of passport as if appeared to be incompatible with passport-steam. I see some examples for authentication on the github of passport-steam if you ever need if for just authenticating users but not getting their details.
Related
I am trying to install visual plug in for my wiki.
during installation i marked nearly all plugins and the result is all available after start.
But i can not save a page via visual.
Because parsoid did not started after installation.
So i decided to install parsoid my self via npm.
I started parsoid now the problem is:
Error contacting the Parsoid/RESTBase server (HTTP 401)
at the same time on the parsoid termina i see the following lines:
at Request._callback (C:\Users\baran\node_modules\parsoid\lib\mw\ApiRequest.js:332:35)\n at Request.self.callback (C:\Users\baran\node_modules\parsoid\node_modules\request\request.js:185:22)\n at Request.emit (events.js:315:20)\n at Request. (C:\Users\baran\node_modules\parsoid\node_modules\request\request.js:1157:10)\n at Request.emit (events.js:315:20)\n at IncomingMessage. (C:\Users\baran\node_modules\parsoid\node_modules\request\request.js:1079:12)\n at Object.onceWrapper (events.js:421:28)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (_stream_readable.js:1327:12)
\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","httpStatus":401,"levelPath":"fatal/request"},"msg":"Your
wiki requires a logged-in account to access the API.","time":"2020-11-17T16:21:29.965Z","v":0}
So the critical line is:
Your wiki requires a logged-in account to access the API
I have installed wiki and parsoid separately how could i enable parsoid to login to the wiki ? ?
Thanx
It is not the correct solution but it is possible to set wiki as "not private" so no need for login for parsoid, and you can protect pages that you don't want other users to modify.
I can't figure out what I've done to mess up Jasmine.
Here's a link to the repo I'm working on:
https://github.com/bryanbeus/04-09-bloccit/tree/v0.1.3
The problem is somehow related to the files /spec/integration/flairs_spec.js, /spec/integration/post_spec.js, and probably more.
The problem can be seen when running a command like npm test. I get the following result:
04-09-bloccit#1.0.0 test /home/siddhartha/Documents/07-Temp/01-Bloc/04-09-bloccit
export NODE_ENV=test && jasmine
npm ERR! Test failed. See above for more details.
It used to be that this ERR would only occur if I had an non-compilable error somewhere in my code. (For example, a simple thing like ; out of place, or an improper use of this.)
Recently, I've heard from someone else that this type of failure for Jasmine isn't normal. Usually, if there's a problem in the code, Jasmine is still supposed to say something. ?
Whatever the problem is, it is now spreading to general usage.
I'm trying to call the server npm module for a test with this command:
const server = require("../../src/server");
If that line is anywhere in my files, the entire Jasmine test fails in the exact same manner. (npm ERR... and no other details.)
If I run npm test /spec/integration/flairs_spec.js with that call to server active, the test fails in the npm ERR... manner.
However, if I comment out the call to server, then Jasmine at least runs. It returns this error:
....................
Started
F
Failures:
1) routes : flairs GET /topics/:topicId/posts/:postId/flairs/new should render a new flair form
Message:
Expected Error: connect ECONNREFUSED 127.0.0.1:3000 to be null.
Stack:
Error: Expected Error: connect ECONNREFUSED 127.0.0.1:3000 to be null.
at
at Request.request.get [as _callback] (/home/siddhartha/Documents/07-Temp/01-Bloc/04-09-bloccit/spec/integration/flairs_spec.js:57:21)
at self.callback (/home/siddhartha/Documents/07-Temp/01-Bloc/04-09-bloccit/node_modules/request/request.js:186:22)
at Request.emit (events.js:160:13)
at Request.onRequestError (/home/siddhartha/Documents/07-Temp/01-Bloc/04-09-bloccit/node_modules/request/request.js:878:8)
at ClientRequest.emit (events.js:160:13)
at Socket.socketErrorListener (_http_client.js:389:9)
at Socket.emit (events.js:160:13)
at emitErrorNT (internal/streams/destroy.js:64:8)
at process._tickCallback (internal/process/next_tick.js:152:19)
Message:
Expected undefined to contain 'New Flair'.
Stack:
Error: Expected undefined to contain 'New Flair'.
at
at Request.request.get [as _callback] (/home/siddhartha/Documents/07-Temp/01-Bloc/04-09-bloccit/spec/integration/flairs_spec.js:58:22)
at self.callback (/home/siddhartha/Documents/07-Temp/01-Bloc/04-09-bloccit/node_modules/request/request.js:186:22)
at Request.emit (events.js:160:13)
at Request.onRequestError (/home/siddhartha/Documents/07-Temp/01-Bloc/04-09-bloccit/node_modules/request/request.js:878:8)
at ClientRequest.emit (events.js:160:13)
at Socket.socketErrorListener (_http_client.js:389:9)
at Socket.emit (events.js:160:13)
at emitErrorNT (internal/streams/destroy.js:64:8)
at process._tickCallback (internal/process/next_tick.js:152:19)
1 spec, 1 failure
Finished in 0.399 seconds
npm ERR! Test failed. See above for more details.
.......
So, removing the server call at least lets Jasmine run.
Any help on this is appreciated. Thank you for helping a novice programmer.
I found the source of the error.
Using git diff v0.1.2..v0.1.3 I was able to see the differences between the last working branch, and the current one.
From here, I saw that in db/src/controllers/flairController.js I had placed this in the controller for the flair object:
const flairQueries = require("./db/queries.flairs.js");
The problem with that is that the directory isn't correct. I replaced it with this:
const flairQueries = require("../db/queries.flairs.js");
After this, the Jasmine test suite worked.
I understand that this means that the controller couldn't load properly. The full understanding of this is still elusive, so if anyone has time to try to explain, I would appreciate it. Otherwise, we can consider this question closed. Thanks!
I am trying to execute some existing code in Node.js on a different system but I am getting an error which I have no clue about.
The system was unable to find the specified registry key or value
When I tried to see the full stack trace, it was:
ERROR: The system was unable to find the specified registry key or value.]
name: [Getter], message: [Getter], code: [Getter] }
ProcessUncleanExitError: QUERY command exited with code 1:
ERROR: The system was unable to find the specified registry key or value.
at mkErrorMsg
(C:\Bhuwan\UFD2_0\API\node_modules\winreg\lib\registry.js:111:12)
at ChildProcess.<anonymous> (C:\Bhuwan\UFD2_0\API\node_modules\winreg\lib\registry.js:459:10)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:821:16)
at Socket.<anonymous> (internal/child_process.js:319:11)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:469:12)
Please note that the code is working just fine on my other system. It is some problem with the current system. Can anyone help me regarding this?
Also, I am using Node v4.3.2 from NVM.
Thanks in advance!
The code is trying to find a registry key telling the Winreg package to find a registry key but can't because it isn't there. But it does exist on the machine that succeeds to run the code. You have to copy the key from the machine that can run the code to the other machine that the code can't run on. For us to give an answer, you need to show us the piece of your code that the error is happening in. find the line that tells the Winreg package to find a certain key. Then your problem can be solved.
node: 0.10.0
npm: 1.2.14
I've set the environment variables HUBOT_FLOWDOCK_LOGIN_EMAIL and HUBOT_FLOWDOCK_LOGIN_PASSWORD, and then tried the following.
Pulled down the prebuilt hubot from the hubot site.
Modified the package.json as above.
Run npm install
Added
"hubot-flowdock": ">= 0.0.1",
just underneath dependencies in my package.json
Removed redis from hubot-scripts.json
run npm install
then running ./bin/hubot -a flowdock -d
With this implementation, ./bin/hubot - flowdock
Produces the following stacktrace:
TypeError: Uncaught, unspecified "error" event.
at TypeError (<anonymous>)
at Session.EventEmitter.emit (events.js:74:15)
at Request._callback (/Users/gb/workspace/hubot-2.2.0/node_modules/hubot-flowdock/node_modules/flowdock/lib/flowdock.js:49:17)
at Request.self.callback (/Users/gb/workspace/hubot-2.2.0/node_modules/hubot-flowdock/node_modules/flowdock/node_modules/request/main.js:122:22)
at Request.EventEmitter.emit (events.js:98:17)
at Request.<anonymous> (/Users/gb/workspace/hubot-2.2.0/node_modules/hubot-flowdock/node_modules/flowdock/node_modules/request/main.js:661:16)
at Request.EventEmitter.emit (events.js:117:20)
at IncomingMessage.<anonymous> (/Users/gb/workspace/hubot-2.2.0/node_modules/hubot-flowdock/node_modules/flowdock/node_modules/request/main.js:623:14)
at IncomingMessage.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:870:14
Looking at /Users/gb/workspace/hubot-2.2.0/node_modules/hubot-flowdock/node_modules/flowdock/lib/flowdock.js:49:17, that is a fail on a response statusCode > 300.
So far so good. Adding a console.log to the line above produces "401" unauthorized.
How? The credentials are correct (I log in with that email/password routinely).
For anyone who cares, eventually I realized that my password was incorrect. I was attempting to use my email password, while the correct answer is to use the password you set up when you first connect to flowdock
I am getting this error when trying to create a message on a queue in azure using node.js azure package version 0.6.6: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
It only happens in the deployed WebRole, but works fine locally and in Azure websites. I need this to be in a webrole as I need to have an SSL certificate.
I deployed the role using this method: https://www.windowsazure.com/en-us/develop/nodejs/tutorials/getting-started/
An error I see in the logs is this which may help diagnose.
Application has thrown an uncaught exception and is terminated:
TypeError: Cannot read property 'statusCode' of null
at E:\approot\node_modules\azure\lib\services\queue\queueservice.js:295:54
at Request._callback (E:\approot\node_modules\azure\lib\services\core\serviceclient.js:197:9)
at E:\approot\node_modules\azure\node_modules\request\main.js:122:22
at Request.<anonymous> (native)
at Request.emit (events.js:67:17)
at ClientRequest.<anonymous> (E:\approot\node_modules\azure\node_modules\request\main.js:224:10)
at ClientRequest.emit (events.js:67:17)
at Socket.socketErrorListener (http.js:1188:9)
at Socket.emit (events.js:67:17)
at Array.0 (net.js:301:14)
I got the answer from posting an issue on the github repo here:
https://github.com/WindowsAzure/azure-sdk-for-node/issues/434
Answer:
I removed the EMULATED env var from web.config before I published. There was a bug (fixed in the 0.6.7 release) that prevented replacing web.cloud.config for web.config
Thanks markcowl!