Closed joes closed 3 months ago
Thanks for the report. We'll get this updated on our docs soon.
Please can this be updated. I noticed the same thing when testing the library this morning.
Hi @samuel-lucas6 ! Our documentation currently builds from a private repository. We've now fixed the issue there, so this should be fixed the next time we rebuild the documentation
Regardless of the challenge type, you must call UseYubiOtp()
when sending a challenge with CalculateChallengeResponse()
(more specifially, call UseYubiOtp(false)
for HOTP and TOTP challenges or UseYubiOtp(true)
for Yubico OTP challenges). There is no default setting; an exception will occur if you do not call UseYubiOtp()
.
Closing now as the docs have now been updated. https://docs.yubico.com/yesdk/users-manual/application-otp/how-to-calculate-a-challenge-response-code.html#settings-and-quirks Thanks for the report @samuel-lucas6 !
I am using v1.9.0 of this SDK:
Your documentation on How to calculate a response code for a challenge-response credential says this about HMAC-SHA1:
And there's also this example for HMAC-SHA1 in the documentation:
However, when I run this
GetDataBytes()
raises the following exception:Thus, it seems that HMAC-SHA1 is not selected by default as the docs will have you believe (or at least not in my case).
The only way I get this to run is by adding
.UseYubiOtp(false)
to the configuration/code as follows: