-
Notifications
You must be signed in to change notification settings - Fork 106
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
Error: InternalOpenIDError: Failed to verify assertion #27
Comments
Did you recently run Are you perhaps redirecting the |
These were only installed today, so no need to update, I also cleared node-gyp to refresh it all, the returnURL is fine as well, the only thing that redirects is when the authentication is successful. |
Is this running off your home computer? If so, are you using a proxy/firewall? |
Nope we're running off of an Ubuntu server with an Nginx reverse proxy in front to manage SSL, load-balancing etc. |
Would it be useful if I attached the executing code where the strategy is configured? |
Yeah, definitely. |
Here is the code:
|
Cool. I'm able to reproduce. Let me look into it. |
Ok thank you! I'm on a deadline for 2 projects with this so thank you very much for the help! To add some more information, I cannot seem to use a database with it, but process.nextTick works, if that may be any use whatsoever, the database definitely works. |
Do you mean the database works within https://nodejs.org/api/process.html#process_process_nexttick_callback_arg |
Hey, so the error you're seeing is kind of unrelated to your issue. For the return route, instead of
You should use:
successRedirect doesn't work for whatever reason (OpenID specific issue probably) which is why you see that error. The method I listed above is the one advocated by the parent dependency FYI, Let me know if this worked out for you. Thanks. |
I don't use |
Hey @aidenwallis, let me know if my solution above worked out for you. Thanks. |
Sadly it didn't resolve the issue :( |
@aidenwallis , here's the code you gave me that I rolled into an Express barebones project and was able to use successfully: https://github.com/welps/aidenwallis Can you try downloading it, configuring it, and verify that it works on your end? |
@welps were you using NPM3? NPM version shouldn't be the issue, but I've got a feeling it may. |
Yeah, I'm on NPM3. I can see that he's on NPM2 from the stack trace, but I'm not sure how NPM can be a factor since the dependencies were just flattened unless there's a conflict. As far as I can tell, it seems like the user's project is still in its infancy so there shouldn't be a load of dependencies yet. |
Just an additional step to debugging. I once experienced issues with NPM2 that were solved by NPM3. You stated you're using NGINX infront, and running a reverse proxy back to the application. Try using the FQDN as the realm and return address, not the IP. |
None of the ideas fixed it, have decided to re-write in PHP for this project. Thank God for being comfortable in multiple languages! :P |
Sorry to hear we couldn't help. I was able to reproduce your issue, remedy it in my dev environment, and repeat it on my staging using the repo I uploaded, so it must be something on your end. Here's the full debug log from my staging:
|
I think I have the same issue trying to implement the open-id authentication in feathersJS. It is working with a simple express app but not with feathers middleware... 😞 |
Hi,
I'm getting this error and I cannot seem to work out why, I'm using MySQL for my database if that's any use.
The text was updated successfully, but these errors were encountered: