asp.net-core-webapi

I have created custom middleware class which validates the JWT token. I am calling this method before app.AddMvc() in configure method. *** I would like to know what are the things that I should add to Configuration services to authenticate my web API using JWT? I have added [Authorize] in my Controller class Do I need to call my middleware class which validates the JWT token first in Configure method? or I should call App.UseAuthentication() I am using the following order : app.UseAuthentication(); app.MessageHandlerMiddleware(); app.UseMvc(); I am new to .net web API implementation. Could

I have a set of WebAPI services in a shared library. These are used in an ASP.NET Core MVC Web Site and dedicated server only hosting the WebAPI Services without the MVC component. Everything works as expected on the MVC Web Site with Unauthorized Requests, I get the 304 redirect to the login page (Account/Login). However when I make an unauthorized request to the WebAPI services, I receive the same 304 redirect to /Account/Login in this case I would like to return the Http 401 Unauthorized result code. I would prefer to not handle this in a custom AuthorizeAttribute but would rather handle at

I'm developing a web application on .Net Core, but as .Net Core is still on development some libraries used are not built on Core yet. I know I can target .Net 4.6 in my application to use old libraries but I'm not sure about what actually change in the use of new .Net Core functionality inside my app. I know this way I'm loosing multi platform capabilities but I actually don't need it at the moment insead I need going on using API and MVC unified pipeline, the integrated dependency Ingnection container and other .Net Core new functionality Will this be aniway possible by targeting old

I've followed several examples suggesting that to set my default route in an ASP.NET Core WebAPI project, I need to replace app.UseMvc(); with app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller}/{action}", defaults: new { controller = "Traders", action = "Get" }); }); But when I run it defaults to localhost:54321/api/values and it should default to localhost:54321/Traders What's wrong? As @tmg mentioned, do the following: Right click your web project -> Select Properties -> Select the Debug tab on the left -> Then edit the 'Launch Url' field to set your own default

I want to create a new Handler that extends DelegatingHandler to enable me to do stuff before getting as far as the controller. I have read in various places that I need need to inherit from DelegatingHandler then overrride SendAsync() like this: public class ApiKeyHandler : DelegatingHandler { protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) { // do custom stuff here return base.SendAsync(request, cancellationToken); } } This is all fine and dandy except it doesn't do anything because I haven't registered it anywhere!

I am using ASP.NET Core 1.0.1. I have the following A class library that uses "Microsoft.AspNetCore.Mvc": "1.0.1" in order to develop my controllers: using System; using System.Collections.Generic; using System.Linq; using System.Threading.Tasks; using Microsoft.AspNetCore.Mvc; namespace CoreAPIsLibrary.Controllers { [Route("api/[controller]")] public class ValuesContoller : Controller { public string Get() { return "value"; } // GET api/values/5 [HttpGet("{id}")] public string Get(int id) { return "value"; } // POST api/values [HttpPost] public void Post([FromBody]string value) { } // PUT api

Using asp.net core web api , I want to have my controller action method to return an jpeg image stream . In my current implementation, browser displays only a json string . My expectation is to see the image in the browser. While debugging using chrome developer tools I found that the content type is still Content-Type:application/json; charset=utf-8 returned in the response header, even though in my code I manually set the content type to "image/jpeg". Looking for a solution My Web API is as below [HttpGet] public async Task<HttpResponseMessage> Get() { var image = System.IO.File.OpenRead("C:

I'm using ASP.NET Core 2.0 application (Web API) as a JWT issuer to generate a token consumable by a mobile app. Unfortunately, this token couldn't be validated by one controller while can be validated by another (using the same validation setting within the same asp.net core 2.0 app). So I have a token which is valid and could be decoded, has all the required claims and timestamps. But one endpoint accepts it, while another gives me 401 error and debug output: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService:Information: Authorization failed for user: (null). [40m[32minfo[39m