OpenID sendToAuthenticationUri lacks promise #379

Merged
merged 1 commit into from Mar 7, 2013

Projects

None yet

2 participants

@genuisereal
Contributor

 Openid module sendToAuthenticationUri step did not provide correct Promise object reference to use inside this.relyingParty.authenticate callback function. Also call back function did not fulfill promise(caused timeout error) and step itself did not return promise reference (caused uncaught exception).

original pull request #287 7 month old

@genuisereal genuisereal OpenID sendToAuthenticationUri lacks promise
 Openid module sendToAuthenticationUri step did not provide correct Promise object reference to use inside this.relyingParty.authenticate callback function. Also call back function did not fulfill promise(caused timeout error) and step itself did not return promise reference (caused uncaught exception).
dabe6fc
@bnoguchi bnoguchi merged commit 9acac6d into bnoguchi:master Mar 7, 2013
@genuisereal genuisereal added a commit to genuisereal/everyauth that referenced this pull request Jun 13, 2013
@genuisereal genuisereal OpenID sendToAuthenticationUri lacks promise
Openid module sendToAuthenticationUri step did not provide correct Promise object reference to use inside this.relyingParty.authenticate callback function. Also call back function did not fulfill promise(caused timeout error) and step itself did not return promise reference (caused uncaught exception).

original pull request #379 which was merged and still this problem arises
d3b9475
@nnghuy nnghuy added a commit to Datahero/everyauth that referenced this pull request Oct 7, 2015
@genuisereal @nnghuy genuisereal + nnghuy OpenID sendToAuthenticationUri lacks promise
Openid module sendToAuthenticationUri step did not provide correct Promise object reference to use inside this.relyingParty.authenticate callback function. Also call back function did not fulfill promise(caused timeout error) and step itself did not return promise reference (caused uncaught exception).

original pull request #379 which was merged and still this problem arises
5dc1aa7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment