gravitational/teleport · error

windows webauthn unavailable in current build

Error message

windows webauthn unavailable in current build

What it means

Build-time sentinel in webauthnwin for non-Windows targets: the native Windows WebAuthn API bindings are replaced by noopNative, so GetAssertion and MakeCredential always return it, signaling the binary lacks Windows WebAuthn support.

Source

Thrown at lib/auth/webauthnwin/webauthn_other.go:31

 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU Affero General Public License for more details.
 *
 * You should have received a copy of the GNU Affero General Public License
 * along with this program.  If not, see <http://www.gnu.org/licenses/>.
 */

package webauthnwin

import (
	"errors"

	wantypes "github.com/gravitational/teleport/lib/auth/webauthntypes"
)

var native nativeWebauthn = noopNative{}

var errUnavailable = errors.New("windows webauthn unavailable in current build")

type noopNative struct{}

func (n noopNative) CheckSupport() CheckSupportResult {
	return CheckSupportResult{
		HasCompileSupport: false,
	}
}

func (n noopNative) GetAssertion(origin string, in *getAssertionRequest) (*wantypes.CredentialAssertionResponse, error) {
	return nil, errUnavailable
}

func (n noopNative) MakeCredential(origin string, in *makeCredentialRequest) (*wantypes.CredentialCreationResponse, error) {
	return nil, errUnavailable
}

View on GitHub (pinned to 1283425b60)

Solutions

1. Run on Windows where the native webauthn.dll bindings are compiled in
2. Use tsh on a platform with a supported WebAuthn implementation, or another MFA method such as OTP

When it happens

Trigger: Thrown at lib/auth/webauthnwin/webauthn_other.go:31 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of gravitational/teleport@1283425b60 (2026-09-02). Data as JSON: /api/errors/7e738c87b8dcd36e. Report an issue: GitHub.