Yes, it's also available on Remote Desktop.

Please see this page for details on using Remote Desktop.

Possible with conditions.

Normally, we sell a YubiKey for YubiOn WindowsLogon Standalone with rewritten key secret information called AES information and provide a license file that only that YubiKey will be able to use. The AES information is necessary for the integrity check of Yubico OTP, but it is not possible to retrieve the AES information from a YubiKey that has been shipped from Yubico. Therefore, it is necessary to rewrite the AES information once, and the rewritten information must be included in the license file.

​

In order to use a YubiKey owned by you, you must provide us with the private key information of the YubiKey to be used in the authentication.

Please check this page for details.​

No separate authentication server is required.

In YubiOn WindowsLogon Standalone, after the input OTP is verified inside the software, the password part is taken over by the normal password check process of Windows. Since OTP verification is completed within the software, there is no need to prepare a new authentication server.

It is available.

In YubiOn WindowsLogon Standalone, after the input OTP is verified inside the software, the password part is taken over by the normal password check process of Windows. The same behavior occurs in the AD environment, and the password check process after OTP verification is normal AD authentication, so it can also be used in the AD environment.

It is also available on Windows Server. Please refer to the product page for details on supported OS.

This is possible by renewing the license.

If you need additional YubiKey, we will sell YubiKey for YubiOn WindowsLogon Standalone again and issue a license file that can be used by those YubiKey. By loading a new license file into the configuration tool, you can increase the available YubiKey with the settings you have already used.

In normal Windows, the ID and password are verified, but in YubiOn WindowsLogon Standalone, the OTP part of the password is verified before the Windows verification process, and if there is no problem, normal Windows authentication is performed. It is a mechanism. Since the second verification item of OTP verification is added while making the best use of the existing Windows mechanism, there is no need to change the existing settings, and the burden on the customer at the time of introduction is reduced.

The most common causes of authentication failure are:

-Input was performed with Caps lock enabled.

-OTP is not output correctly due to poor contact between the USB port of the terminal or the USB hub. 

[One-time password output confirmation method]

1. Insert YubiKey into the USB port.

2. Open a text editor.

3. Touch the metal part of YubiKey.

→ It is normal if a 44-character character string is output. (Half-width input)

YubiOn WIndowsLogon Standalone has the ability to hide itself from the list of installed applications. (Uninstall control function)

Start the setting tool and check the "Uninstall control" item in "Operation settings". If it seems to be "on", you can display it in the application list by turning it "off".

YubiKey recognizes it as a keyboard device. It can be used if the USB keyboard is permitted.

For AD accounts, "AD accounts that have logged on once" are targeted. After logging on with the AD account you want to set once, set the assignment with the setting tool. If secure mode is on, log on with a password after setting it to off, and then set it.

Yes, it works. If secure mode is on, YubiKey is required at logon even when booting in safe mode. If secure mode is off, you can log on with only a password when booting in safe mode.

If you are using antivirus software, it may restrict the operation of YubiOn. Please exclude the following files from your antivirus software before installing YubiOn.

- Target files

C:\Program Files\YubiOn\Standalone\StandaloneAdministrateTool\ControlzEx.dll
C:\Program Files\YubiOn\Standalone\StandaloneAdministrateTool\log4net.dll
C:\Program Files\YubiOn\Standalone\StandaloneAdministrateTool\MahApps.Metro.dll
C:\Program Files\YubiOn\Standalone\StandaloneAdministrateTool\Microsoft.Practices.ServiceLocation.dll
C:\Program Files\YubiOn\Standalone\StandaloneAdministrateTool\Microsoft.Xaml.Behaviors.dll
C:\Program Files\YubiOn\Standalone\StandaloneAdministrateTool\Prism.Desktop.Net40.dll
C:\Program Files\YubiOn\Standalone\StandaloneAdministrateTool\StandaloneCommon.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\CredentialProviderCommon.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\log4net.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\StandaloneCommon.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\StandaloneCredentialProvider.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\Vanara.Core.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\Vanara.PInvoke.Kernel32.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\Vanara.PInvoke.Security.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\Vanara.PInvoke.Shared.dll
C:\Program Files\YubiOn\Standalone\StandaloneCredentialProvider\ja\StandaloneCredentialProvider.resources.dll
C:\Program Files\YubiOn\Standalone\StandaloneService\log4net.dll
C:\Program Files\YubiOn\Standalone\StandaloneService\StandaloneCommon.dll
C:\Program Files\YubiOn\Standalone\StandaloneSetupTool\ControlzEx.dll
C:\Program Files\YubiOn\Standalone\StandaloneSetupTool\log4net.dll
C:\Program Files\YubiOn\Standalone\StandaloneSetupTool\MahApps.Metro.dll
C:\Program Files\YubiOn\Standalone\StandaloneSetupTool\Microsoft.Practices.ServiceLocation.dll
C:\Program Files\YubiOn\Standalone\StandaloneSetupTool\Microsoft.Xaml.Behaviors.dll
C:\Program Files\YubiOn\Standalone\StandaloneSetupTool\Prism.Desktop.Net40.dll
C:\Program Files\YubiOn\Standalone\StandaloneSetupTool\StandaloneCommon.dll