@jeremydmiller ah yes you are right, so i think the issue is something else basically i was writing a test for the Add method on this controller https://github.com/joaofbantunes/OOPsIDidItAgain/blob/main/src/OOPsIDidItAgain.06.MinimizingExceptions.Web/Controllers/CartsController.cs
it has input param AddItemCartModel which looks like https://bit.ly/2OWlYHx the ItemId field is another type and that is hydrated by https://bit.ly/3tn7oYo modelbinder and i think issue is here
Hey, if anybody is paying attention to this, here's a set of proposed changes for Alba V5: JasperFx/alba#86
The big driver is wanting helpers for testing APIs secured by JWTs post haste at my work
s.PostConfigure<JwtBearerOptions>(JwtBearerDefaults.AuthenticationScheme, options =>
{
options.TokenValidationParameters = new TokenValidationParameters
{
IssuerSigningKey = FakeJwtGenerator.SecurityKey,
ValidIssuer = FakeJwtGenerator.Issuer,
ValidAudience = FakeJwtGenerator.Audience
};
});
Although in our case our identity provider is Auth0, so I'm guessing there's some extra complexity when it comes to IdentityServer.
I'm overriding the token validation, so as long as the rest of the data on the token meets the authorization requirements we're all good.
How are you overriding the token validation?
My Startup.cs contains
services.AddAuthentication(options =>
{
options.DefaultAuthenticateScheme = JwtBearerDefaults.AuthenticationScheme;
options.DefaultChallengeScheme = JwtBearerDefaults.AuthenticationScheme;
})
.AddJwtBearer(options =>
{
options.Authority = Configuration["Auth0:Domain"];
options.Audience = Configuration["Auth0:Audience"];
})PostConfigure runs after the bearer options were set, thereby wiping out the configuration and validating the token with the fake signing key instead of reaching out and getting the JWKs from Auth0.
Also, doing difficult exploratory coding while watching Peppa Pig with a sick 4yo hanging on your arm is not terribly effective.
The simple thing I haven't tried yet is just sticking a ClaimsPrincipal on the HttpContext first.
// This will deactivate the callout to the OIDC server
options.ConfigurationManager =
new StaticConfigurationManager<OpenIdConnectConfiguration>(new OpenIdConnectConfiguration
{
});
@Hawxy Can you peek at this one? https://jeremydmiller.com/2021/08/09/testing-web-services-secured-by-jwt-tokens-with-alba-v5/
NRTs was already enabled at the assembly level as part of v4: https://github.com/JasperFx/alba/blob/master/src/Alba/Alba.csproj#L18
.NET 6 project templates will also ship it enabled by default going forward
It'd be good to get JasperFx/baseline#23 in, as it's a blocker for NRT accuracy within all of the dependents.
Hi. I'm using AlbaHost to test our endpoints, but I'm having some trouble with IScenarioResult's readers. I have content in the body, there's a content length, and a content-type of application/json. But the result's ReadAsJson comes back as null. When I force the response body into a stream reader I get the full body back.
ReadAsText also comes back empty.
On the response coming back? How is the body written in the real request? Is it a 200 response? You can see that there’s non-zero content in the Response body stream?
ReadAsText() is just rewinding the Response body and pulling the string out. Are you completely sure there’s actually bytes written to the response body?
yes, the response coming back. 200, .Context.Response.Headers.ContentLength. Used StreamReader and got back a full JSON string. ReadAsText resulted in an empty string from the IScenarioResult. Of course, reading the bytes directly causes the stream to not be readable the second time though.
I was thinking there was something not set up correctly on our end.
I think maybe I had kept the ReadAsJson in the code previously, and that stopped it from reading text.