Cannot set OTP locking code in YK Manager after configuring token with Windows Authenticator

[wagner-robert]

Using the latest Windows Authenticator - 7.2.3
Latest YK Manager
Token - FIPS v5

Using a blank token, setup token for Windows Authentication. Switch to YK Manager - Command line, then try and set OTP Slot 1 locking code. Permission failure.

The token, configuration and locking code works fine if OTP Challenge is configured in manager and imported in the Windows Authenticator.

Is anyone else seeing this problem?

[wagner-robert]

Our Oath best practice is to set the slot locking code after configuration. We would like to request the ability to set the slot locking code after configuration. Having to switch to the manager is clunky.

[dainnilsson]

It's unclear to me if you're talking about the OATH application, with codes displayed in Yubico Authenticator, or Yubico OTP slots (short and long press), or something else (and thus the slot access codes or the OATH password). Can you elaborate more on what you are using and what you are trying to do?

[wagner-robert]

Please reach out to Adam D. Oliver - yubico. He is familiar with this issue and has been able to reproduce it.