JwtBearerOptions - token validation offline or online? RRS feed

  • Question

  • User-50787436 posted

    Hi all,

    I'm working on ASP.Net Core 3.1 for API development, and I was adding logic to validate Bearer tokens, I'm quite new on this and found out logic like this:

    public static void AddAuthentication(this IServiceCollection services, IConfiguration config)
                .AddJwtBearer(options =>
                    options.Authority = "https://loremipsum.com";
                    options.RequireHttpsMetadata = true;
                    options.Audience = "LoremIpSum";
                    options.SaveToken = true;
                    options.TokenValidationParameters = new TokenValidationParameters
                        ValidateActor = true,
                        ValidateIssuer = true,
                        ValidateAudience = true,
                        ValidateLifetime = true,
                        RequireExpirationTime = true,
                        ValidIssuer = "https://loremipsum.com",
                        NameClaimType = "name"
                .AddCookie(options => options.SlidingExpiration = true);

    I was wondering, this allows me to specify some options, but how can I tell to validate tokens offline or online?

    Or by default this provides logic only for online validation?

    This might be a rookie question and it may be quite simple but I'm not following :(

    Monday, May 4, 2020 9:32 AM


All replies

  • User-854763662 posted

    Hi pacojones,

    I'm not familar with JwtBear Token , for Offline Token Validation , the follwoing microsoft official blog may be helpful:


    Best Regards,


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, May 5, 2020 8:19 AM
  • User-474980206 posted

    The typical case is that the asp.net core site is creating the bearer token, so it can validate (knows the signing key). If the bearer token is from another source, then you will need to write custom validation logic. 

    Tuesday, May 5, 2020 3:01 PM