Receiving error_description="The signature key was not found" from API call when hosting on one App Service, but not when I run same app locally or on different Azure App Services.

Question

Receiving error_description="The signature key was not found" from API call when hosting on one App Service, but not when I run same app locally or on different Azure App Services.

Colgrove, Steven 0

I have an API application that I am trying to get configured to work with a new client application. I have everything set up to work when I run it locally, on a separate Dev App Service, and on a "staging" slot of my Production App Service. However, when I swap (or push directly) to my Production App Service I receive an error when trying to consume the API: Bearer error="invalid_token", error_description="The signature key was not found".

I have checked various configurations and everything appears to be the same and the code running should be the same... What might be causing this issue?

Anonymous

2024-08-15T13:37:08.2066667+00:00

Hi @Colgrove, Steven,

Please share the settings in TokenValidationParameters. And I think maybe the settings is different between Dev and Production.

Best Regards

Jason
Colgrove, Steven 0 Reputation points

2024-08-15T14:42:19.77+00:00
Thanks for the response. The settings shouldn't be different at this point. I just have 1 appsettings.json file that I have confirmed to exist correctly in each of the environments. It has the B2C section defined as

"B2C": { "Issuer": "https://{tenantName}.b2clogin.com/{tenantID}/v2.0/", "Audience": "{applicationId}", },

And I am using them in my TokenValidationParameters with:

options.TokenValidationParameters = new Microsoft.IdentityModel.Tokens.TokenValidationParameters() { ValidIssuer = Configuration.GetSection("B2C").GetValue<string>("Issuer"), ValidAudience = Configuration.GetSection("B2C").GetValue<string>("Audience") };

Perhaps I don't have it fully configured correctly, but I would still expect it to either always work or never work the way it is configured. The fact it works everywhere except where I want has me perplexed.

The application has been running with other settings and this section is new to the file. I will push an update that I can use to read another new variable I insert into the appsettings file just to confirm that it is using the updated file.

Your answer

Anonymous

2024-08-15T13:37:08.2066667+00:00

Hi @Colgrove, Steven,

Please share the settings in TokenValidationParameters. And I think maybe the settings is different between Dev and Production.

Best Regards

Jason
Colgrove, Steven 0 Reputation points

2024-08-15T14:42:19.77+00:00

Thanks for the response. The settings shouldn't be different at this point. I just have 1 appsettings.json file that I have confirmed to exist correctly in each of the environments. It has the B2C section defined as

"B2C": { "Issuer": "https://{tenantName}.b2clogin.com/{tenantID}/v2.0/", "Audience": "{applicationId}", },

And I am using them in my TokenValidationParameters with:

options.TokenValidationParameters = new Microsoft.IdentityModel.Tokens.TokenValidationParameters() { ValidIssuer = Configuration.GetSection("B2C").GetValue<string>("Issuer"), ValidAudience = Configuration.GetSection("B2C").GetValue<string>("Audience") };

Perhaps I don't have it fully configured correctly, but I would still expect it to either always work or never work the way it is configured. The fact it works everywhere except where I want has me perplexed.

The application has been running with other settings and this section is new to the file. I will push an update that I can use to read another new variable I insert into the appsettings file just to confirm that it is using the updated file.

Share via

Receiving error_description="The signature key was not found" from API call when hosting on one App Service, but not when I run same app locally or on different Azure App Services.

Your answer