IDX10500: Signature validation failed. No security keys were provided to validate the signature. in the server log means the JWT bearer handler had no key at all to check the token with. Give it one: set IssuerSigningKey in TokenValidationParameters.

The client cannot tell this case apart from a wrong key: the response header says The signature key was not found in both. Only the IDX code in the server console tells you whether the API had no key (IDX10500) or a different one (IDX10517).

The error

The response, from curl.exe -i, with a valid test token:

curl.exe -i http://127.0.0.1:15603/patients -H "Authorization: Bearer $token"
HTTP/1.1 401 Unauthorized
Content-Length: 0
Date: Sat, 14 Nov 2026 01:13:41 GMT
Server: Kestrel
WWW-Authenticate: Bearer error="invalid_token", error_description="The signature key was not found"

The server console:

info: Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler[1]
      Failed to validate the token.
      Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException: IDX10500: Signature validation failed. No security keys were provided to validate the signature.
...

Why it happens

This instance was started with --Lab:NoKey=true, which skips the IssuerSigningKey line, and it has no Authority either, so the handler has nothing to compare the signature with. Look for the place in your own code where TokenValidationParameters is built and check that the key is set on every path.

A second cause: an Authority where nothing answers

A third instance had no local key and Authority set to http://127.0.0.1:15609, a port where nothing listened (with RequireHttpsMetadata = false, since the address is http). The same token got the same 401, and the console printed the same IDX10500 line, with no separate line about the metadata download. A rerun on port 15607 with Default, Microsoft.AspNetCore and Microsoft.AspNetCore.Authentication all at Trace printed the same IDX10500 lines and still no line about 15609 or the metadata:

curl.exe -i http://127.0.0.1:15606/patients -H "Authorization: Bearer $token"
HTTP/1.1 401 Unauthorized
...
WWW-Authenticate: Bearer error="invalid_token", error_description="The signature key was not found"

So when an API that relies on an identity server starts answering with IDX10500, check that the identity server's address in Authority is reachable from the API's machine.

The fix

The key lines from the test's Program.cs (the key is a made-up test string in appsettings.json):

        if (builder.Configuration["Lab:NoKey"] != "true")
        {
            parameters.IssuerSigningKey = new SymmetricSecurityKey(
                Encoding.UTF8.GetBytes(builder.Configuration["Jwt:Key"]!));
        }

A token minted the same way, against the instance that has the key (port 15600):

curl.exe -i http://127.0.0.1:15600/patients -H "Authorization: Bearer $token"
HTTP/1.1 200 OK
...
["Maria Garcia","David Chen"]

If the key comes from configuration, fail at start-up when it is missing instead of letting every request fail later, for example with a null check on the value before AddJwtBearer.

How it was reproduced

A dotnet new web -f net10.0 API with Microsoft.AspNetCore.Authentication.JwtBearer 10.0.15 (Microsoft.IdentityModel 8.19.2) and one endpoint protected with RequireAuthorization(), on the ASP.NET Core 10.0.15 runtime, SDK 11.0.100, the Microsoft.AspNetCore.Authentication log category at Information. Four instances on 127.0.0.1: 15600 with the key, 15603 without it, 15606 without it and with the dead authority, 15607 like 15606 with Trace logging. The token came from a console project on System.IdentityModel.Tokens.Jwt 8.19.2; requests went through curl 8.22.0 on Windows.

Frequently asked

What does IDX10500 No security keys were provided mean?
The JWT bearer handler had no signing key to validate with: no IssuerSigningKey and no keys from an Authority. In the test the client saw a 401 with The signature key was not found.
Why does IDX10500 appear when I use an Authority?
In the test, an Authority on a port where nothing answered gave the same IDX10500 line and the same 401. Check that the API can reach the identity server's address.
How do I tell IDX10500 from IDX10517?
Only in the server log. The response header was The signature key was not found in both cases; IDX10500 means no key at all, IDX10517 means the keys tried did not match.

More decoded errors in the Fixes category. The case with a key that does not match is IDX10517.