Failed to discover OP endpoint URL
See original GitHub issueUsing the recommended code
passport.use(new SteamStrategy({
returnURL: 'http://mysite.com/auth/steam/return',
realm: 'http://mysite.com/',
apiKey: 'my key'
},
etc.
app.use('/auth/steam',
passport.authenticate('steam', { successRedirect: '/',
failureRedirect: '/error' })
);
app.use('/auth/steam/return',
passport.authenticate('steam', {failureRedirect: '/404' }),
function(req, res) {
res.redirect('/');
}
);
Error: Failed to discover OP endpoint URL (message: No providers found for the given identifier)
Occasionally the site will progress past this stage however, resulting in the next error:
Failed to verify assertion (message: No OpenID provider was discovered for the asserted claimed identifier)
I tried the solution in #27 but I couldn’t get it to work. Has anyone gained any further understanding on this issue?
To add to this, this has been working in my app for 8 months or so, none of the code has been changed.
Issue Analytics
- State:
- Created 7 years ago
- Comments:16
Top Results From Across the Web
Failed to discover OP endpoint URL (message: No providers ...
When I enter a bad openid URL , passport-openid responds with 500 Failed to discover OP endpoint URL (message: No providers found for...
Read more >Failed to discover OP endpoint - node.js - Stack Overflow
I've ported sample yahoo passport code to my project. Always get "Failed to discover OP endpoint" error, when click on "Sign On with...
Read more >Steam OAuth issues the last couple of days. | Screeps Forum
InternalOpenIDError: Failed to discover OP endpoint URL ... up on another Oauth error (https://screeps.com/api/auth/steam/return?openid.ns=.
Read more >Failed to discover OP endpoint URL : passport-ibm
We have a Node.js application hosted on Bluemix. It uses IBM Tivoli Federated Identity Manager as the authentication service and uses OpenID ...
Read more >OpenID Connect Discovery - Swagger
This URL returns a JSON listing of the OpenID/OAuth endpoints, supported scopes and claims, public keys used to sign the tokens, and other...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Never mind, dug a bit deeper, Firebase dont allow external API calls on free trier, upgrading to a paid plan fixed the issue
I have this error only on 1 server of 3. Two servers work correctly, pointing directly the single server URL, fire the error. i would appreciate if someone can point me in the right direction.
Express, Nodejs and packages are the same, only Ubuntu version is different, the not working server is newer. NTP is on and synced, the time is correct.
Thanks