Bearer error="invalid_token", error_description="The issuer 'https://login.other.test' is invalid" means the token's iss claim is not the issuer the API accepts. Issue the token with the issuer configured in ValidIssuer and the request is accepted.

Unlike the audience check, this one names the wrong value in the response, and the server log (IDX10205) prints both the token's issuer and the issuer it expected. Copy the expected value from that log line into whatever issues the token.

The error

The response, from curl.exe -i:

$token = .\mint\bin\Debug\net10.0\Mint.exe "fix11-test-only-signing-key-0123456789abcdef" https://login.other.test fix11-api 30 0
curl.exe -i http://127.0.0.1:15600/patients -H "Authorization: Bearer $token"
HTTP/1.1 401 Unauthorized
Content-Length: 0
Date: Sat, 14 Nov 2026 01:13:01 GMT
Server: Kestrel
WWW-Authenticate: Bearer error="invalid_token", error_description="The issuer 'https://login.other.test' is invalid"

The server console:

info: Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler[1]
      Failed to validate the token.
      Microsoft.IdentityModel.Tokens.SecurityTokenInvalidIssuerException: IDX10205: Issuer validation failed. Issuer: 'https://login.other.test'. Did not match: validationParameters.ValidIssuer: 'https://issuer.test' or validationParameters.ValidIssuers: 'null' or validationParameters.ConfigurationManager.CurrentConfiguration.Issuer: 'Null'. For more details, see https://aka.ms/IdentityModel/issuer-validation.
...

Why it happens

The token maker wrote https://login.other.test into iss; the API accepts only https://issuer.test. The log lists the three places the handler compared against: ValidIssuer, ValidIssuers (null here) and the issuer from downloaded metadata (null here; the test sets no Authority).

When you meet this error in a real project, put the two values from the log line next to each other and look at the scheme, the host and any trailing slash or path. The value in the token is the one the issuer actually wrote, and the value after ValidIssuer is the one your API reads from its own configuration, so the log line tells you which side's setting to change.

The fix

The API's settings in the test's Program.cs:

        var parameters = new TokenValidationParameters
        {
            ValidIssuer = "https://issuer.test",
            ValidAudience = "fix11-api",
        };

A token minted with that issuer:

$token = .\mint\bin\Debug\net10.0\Mint.exe "fix11-test-only-signing-key-0123456789abcdef" https://issuer.test fix11-api 30 0
curl.exe -i http://127.0.0.1:15600/patients -H "Authorization: Bearer $token"
HTTP/1.1 200 OK
...
["Maria Garcia","David Chen"]

Turning ValidateIssuer off would also hide the 401, at the cost of accepting a token from any issuer that holds the signing key; it is not the fix and was not tested here.

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 127.0.0.1:15600 with the ASP.NET Core 10.0.15 runtime and SDK 11.0.100. A console project on System.IdentityModel.Tokens.Jwt 8.19.2 made HS256 tokens with a chosen key, issuer, audience and lifetime; the key and both issuer names are made up for the test. Requests went through curl 8.22.0 on Windows, and the Microsoft.AspNetCore.Authentication log category was set to Information.

Frequently asked

What does IDX10205 Issuer validation failed mean?
The iss claim in the token did not match ValidIssuer, ValidIssuers or the issuer from the authority's metadata. The log line prints the token's issuer and every value it was compared with.
Where do I see which issuer ASP.NET Core expected?
In the server console, in the IDX10205 line, at Information level for Microsoft.AspNetCore.Authentication. The response header only names the token's issuer.
How do I fix 'The issuer is invalid' in ASP.NET Core?
Make the token's iss claim equal the API's ValidIssuer. In the test, minting the token with https://issuer.test instead of https://login.other.test turned the 401 into a 200.

More decoded errors in the Fixes category. The audience check fails with less to go on: The audience '(null)' is invalid (IDX10214).