You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The aforementioned line of code is responsible to request the current state of a challenge, which seems to be undefined behavior regarding to RFC8555. The RFC suggests, clients will use the authorization url to request the current state of the authorization process (https://www.rfc-editor.org/rfc/rfc8555#section-7.5.1).
The challenge url is used to signal, which challenge should be processed only - not to request the state of that particular challenge.
As maintainer of an acme-server component, an issue has been brought to my attention, which seems to orgininate here:
https://github.com/acmesh-official/acme.sh/blob/master/acme.sh#L5032
The aforementioned line of code is responsible to request the current state of a challenge, which seems to be undefined behavior regarding to RFC8555. The RFC suggests, clients will use the authorization url to request the current state of the authorization process (https://www.rfc-editor.org/rfc/rfc8555#section-7.5.1).
The challenge url is used to signal, which challenge should be processed only - not to request the state of that particular challenge.
The original issue was raised here: glatzert/ACME-Server-ADCS#8 - it contains the debug log as well.
The text was updated successfully, but these errors were encountered: