réplica de
https://github.com/therootcompany/acme.js.git
sincronizado 2024-11-16 17:29:00 +00:00
Handle case where the returned auth is already valid
At least for Buypass, if one already has previously validated an authorization on that ACME account for a requested domain name, the initial status when created is "valid". However, the code was trying to submit the challenge for validation anyway, causing the server to return "status:400 Unable to process challenge, authorization is not pending". So, if the initial status is valid, it should just proceed rather than trying to process the challenge again. I'm not sure if this is exactly the best way to write this, but it seems to work for me on both Let's Encrypt and Buypass.
Este cometimento está contido em:
ascendente
45fd6962f2
cometimento
0d20643826
4
acme.js
4
acme.js
@ -855,7 +855,11 @@ ACME._postChallenge = function (me, options, kid, auth) {
|
|||||||
.catch(transformError);
|
.catch(transformError);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
if (auth.status === 'valid') {
|
||||||
|
return pollStatus();
|
||||||
|
} else {
|
||||||
return respondToChallenge();
|
return respondToChallenge();
|
||||||
|
}
|
||||||
};
|
};
|
||||||
|
|
||||||
// options = { domains, claims, challenges }
|
// options = { domains, claims, challenges }
|
||||||
|
Carregando…
x
Criar uma nova questão referindo esta
Bloquear um utilizador