Files
Oleksandr Bezdieniezhnykh f979e18811 [AZ-494] Enable JWT iss/aud validation with fail-fast startup
Option B per user decision: production ships with empty Jwt.Issuer /
Jwt.Audience in appsettings.json so the API process refuses to start
unless JWT_ISSUER + JWT_AUDIENCE env vars are supplied. Development
ships with grep-friendly DEV-ONLY- placeholders so local + docker
flows keep working unchanged.

AuthenticationServiceCollectionExtensions flips ValidateIssuer +
ValidateAudience to true and wires ValidIssuer / ValidAudience via a
new ResolveRequiredOrThrow helper that all three required values
(secret, iss, aud) now share. JwtTokenFactory.Create + CreateExpired
gain optional iss / aud parameters (default null) so existing call
sites compile unchanged. JwtTestHelpers adds MintAuthenticated /
MintExpired wrappers that resolve iss + aud from env, plus
ResolveIssuerOrThrow / ResolveAudienceOrThrow. PerfBootstrap.MintToken
+ Program.cs JWT bootstrap migrated to the new surface so the perf
harness and the integration runner both validate against the same
contract.

Adds 4 fail-fast unit tests (missing/empty issuer + audience), 2
negative integration scenarios (WrongIssuer_Returns401,
WrongAudience_Returns401), and re-tags every existing integration
mint site via MintAuthenticated.

Compose, .env.example, run-tests.sh, run-performance-tests.sh all
load + export JWT_ISSUER + JWT_AUDIENCE alongside JWT_SECRET.

Resolves F-AUTH-2 (security_report.md + owasp_review.md). AC-7
(cross-repo suite/_docs/10_auth.md write) deferred — outside this
workspace; tracked in deploy_cycle2.md R3 follow-up.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-12 02:28:48 +03:00

85 lines
2.8 KiB
C#

using System.IdentityModel.Tokens.Jwt;
using System.Security.Claims;
using System.Text;
using Microsoft.IdentityModel.Tokens;
namespace SatelliteProvider.TestSupport;
public static class JwtTokenFactory
{
public const string DefaultSubject = "test-user";
public static string Create(
string secret,
string subject = DefaultSubject,
TimeSpan? lifetime = null,
IEnumerable<Claim>? extraClaims = null,
string algorithm = SecurityAlgorithms.HmacSha256,
string? issuer = null,
string? audience = null)
{
ArgumentNullException.ThrowIfNull(secret);
var keyBytes = Encoding.UTF8.GetBytes(secret);
var signingKey = new SymmetricSecurityKey(keyBytes);
var credentials = new SigningCredentials(signingKey, algorithm);
var now = DateTime.UtcNow;
var expires = now.Add(lifetime ?? TimeSpan.FromHours(1));
// JwtSecurityToken rejects Expires <= NotBefore. For negative
// lifetimes (expired-token test fixture) shift NotBefore behind
// Expires so the constructor accepts the token and lifetime
// validation can fire downstream. DO NOT remove this branch —
// see cycle-2 commits f64d0d7 + 11b7074 (LESSONS.md L-testing).
var notBefore = expires <= now ? expires.AddMinutes(-5) : now;
var claims = new List<Claim>
{
new(JwtRegisteredClaimNames.Sub, subject),
new(JwtRegisteredClaimNames.Jti, Guid.NewGuid().ToString("N"))
};
if (extraClaims is not null)
{
claims.AddRange(extraClaims);
}
var token = new JwtSecurityToken(
issuer: issuer,
audience: audience,
claims: claims,
notBefore: notBefore,
expires: expires,
signingCredentials: credentials);
return new JwtSecurityTokenHandler().WriteToken(token);
}
public static string CreateExpired(string secret, string subject = DefaultSubject, string? issuer = null, string? audience = null)
{
return Create(secret, subject, lifetime: TimeSpan.FromMinutes(-5), issuer: issuer, audience: audience);
}
public static string TamperSignature(string token)
{
ArgumentException.ThrowIfNullOrEmpty(token);
var parts = token.Split('.');
if (parts.Length != 3)
{
throw new ArgumentException("JWT must have three dot-separated parts.", nameof(token));
}
var signature = parts[2];
if (signature.Length == 0)
{
throw new ArgumentException("JWT signature segment is empty.", nameof(token));
}
var firstChar = signature[0];
var replacement = firstChar == 'A' ? 'B' : 'A';
parts[2] = replacement + signature[1..];
return string.Join('.', parts);
}
}