.NET Framework is a topic the MagnusMinds engineering team writes about from project work: how it is set up, where it breaks, and what we changed in production. This tag page lists all 11 articles tagged .NET Framework.
Start with “Hosting a .NET Application on IIS Server” or “Quick Tips: Managing Expired Tokens”. Open a post for the full write-up, or follow another tag or category on the card to a related topic.
Hosting your .NET application on an IIS (Internet Information Services) server allows it to be accessed and consumed over the internet by users. IIS is commonly used to host .NET applications and web APIs. Before you can host the application, ensure you have the following: A .NET web application or API built (for example using ASP.NET Core) A Windows Server machine with IIS installed and configured Permissions to remotely access the server over a network Follow this step-by-step guide to deploy your .NET Application on the IIS Server seamlessly. Step 1: Open your .NET Application in Visual Studio Open your application or project in Visual Studio and build the application. Step 2 : Publish the Application or project. Now, Right-click on your project and select the publish option. Here, select the folder and then click on next, and finish the publish setup. Now, Click on the publish button to publish your code to one folder. After, publishing is succeeded click on the open folder. You will see your published code in this folder. Step 3: Configure IIS on the Server Carry out these steps to prepare IIS for hosting the application. If IIS is not installed in your system, then first install the IIS on your machine. Open IIS Manager on the Windows Server Right-click on the Sites folder and click Add Website 3. Provide a name for the website, Set the physical path to the app folder, and select a port where you want to host the application. 4. Click OK to create the new IIS website. Step 4: Publish code to IIS Server. Now stop the website and open the folder that you have given in the Physical path while configuring it, by right-clicking on your website and selecting explore. Now, copy all the published files into your server folder. Once all the files are copied into the publish folder Start the website and click on Browse*: {Your port} (http) under browse website. you will see the output of your code on the server. If your project is based on MVC then Recycle Application pool is required. You can find your Application pool under the Application Pool section. Right-click on your website app pool and click on recycle. Conclusion: Hosting the application on IIS allows it to be reached by users from over the network and the internet. It handles request routing and security layers for serving the application.
Here, I will explain how to restrict users from using expired tokens in a .NET Core application. Token expiration checks are crucial for ensuring the security of your application. Here's a general outline of how you can achieve this: 1. Configure Token Expiration: When generating a token, such as a JWT, set an expiration time for the token. This is typically done during token creation. For example, when using JWTs, you can specify the expiration claim: var tokenDescriptor = new SecurityTokenDescriptor { Expires = DateTime.Now.AddMinutes(30) // Set expiration time }; 2. Token Validation Middleware: Create middleware in your application to validate the token on each request. This middleware should verify the token's expiration time. You can configure this middleware in the startup or program file on the .NET side. public void Configure(IApplicationBuilder app, IHostingEnvironment env) { app.UseMiddleware<TokenExpirationMiddleware>(); } 3. Token Expiration Middleware: Develop middleware to validate the token's expiration time. Take note of the following points: ValidateIssuerSigningKey: Set to true, indicating that the system should validate the issuer signing key. IssuerSigningKey: The byte array represents the secret key used for both signing and verifying the JWT token. ValidateIssuer and ValidateAudience: Set to false, indicating that validation of the issuer and audience is skipped. By setting ClockSkew to TimeSpan.Zero, you specify no tolerance for clock differences. If the current time on the server or client is not precisely within the token's validity period, the token is considered expired. public class TokenExpirationMiddleware { private readonly RequestDelegate _next; public TokenExpirationMiddleware(RequestDelegate next) { _next = next; } public async Task Invoke(HttpContext context) { // Check if the request has a valid token var token = context.Request.Headers["Authorization"].FirstOrDefault()?.Split(" ").Last(); if (token != null) { var tokenHandler = new JwtSecurityTokenHandler(); var key = Encoding.ASCII.GetBytes("YourSecretKey"); // Replace with your actual secret key of Issuer var tokenValidationParameters = new TokenValidationParameters { ValidateIssuerSigningKey = true, IssuerSigningKey = new SymmetricSecurityKey(key), ValidateIssuer = false, ValidateAudience = false, ClockSkew = TimeSpan.Zero }; try { // Validate the token var principal = tokenHandler.ValidateToken(token, tokenValidationParameters, out var securityToken); // Check if the token is expired if (securityToken is JwtSecurityToken jwtSecurityToken) { if (jwtSecurityToken.ValidTo < DateTime.Now) { // Token is expired context.Response.StatusCode = (int)HttpStatusCode.Unauthorized; return; } } } catch (SecurityTokenException) { // Token validation failed context.Response.StatusCode = (int)HttpStatusCode.Unauthorized; return; } } await _next(context); } } Working fine with proper token time. Here is an example: I am providing an expired token, and it will result in a 401 Unauthorized status. You can also check the token in https://jwt.io/ for time expired (exp) . By following these steps, you can effectively implement checks to ensure that users are not able to use expired tokens within your .NET Core application.
