asp.net-web-api2

问题 The Scenario I've recently built an ASP.NET WEB API , and have protected its resources using OAuth Bearer Access Tokens. I've used the Client_Credentials Flow, as it will be accessed by clients as opposed to users. Here's the thing, when a client has successfully provided the client_id and the client_secret they receive a response like the following :- { "access_token": "<Access Token>", "token_type": "bearer", "expires_in": 1199, "refresh_token": "<Refresh Token>" } Refresh Tokens. Not

问题 I'm having trouble figuring out how to get the Help page in my Web Api to show anything for Resource Description other than None. It has IHttpActionResult linked and then "None." after that. I got my samples working by adding config.SetActualResponseType(typeof(ComplexType), "Controller", "Action"); to HelpPageConfig.cs. My controller looks like this: /// <summary> /// My description /// </summary> [Route("MyRoute")] public IHttpActionResult Get() { try { //throw new Exception("TEST"); return

问题 Trying to move from OData v3 to OData v4 . Why do I keep getting a 404 when trying to use OData Functions ? Web API Config: ODataModelBuilder builder = new ODataConventionModelBuilder(); //etc builder.EntitySet<LocalizableString>("LocalizableStringApi"); //etc var getComparitiveTableFunction = builder.EntityType<LocalizableString>().Collection.Function("GetComparitiveTable"); getComparitiveTableFunction.Parameter<string>("cultureCode"); getComparitiveTableFunction.ReturnsCollection

问题 I have created a Web API 2 project and although the APIs work fine, I must enter a trailing slash for them to do so. This results in a 404 http://www.myURL.com/api/v1/get/addressfromlatlong/UK/50.9742794/-0.1146699 This shows the JSON response as intended http://www.myURL.com/api/v1/get/addressfromlatlong/UK/50.9742794/-0.1146699/ I have another controller with a custom action that works fine. The only difference is that this has one parameter that is an integer... It seems to be something to

问题 What is the difference between the following two ways of accessing the principle via an AuthorizeAttribute implementation? Using HttpContext : protected override bool IsAuthorized(HttpActionContext actionContext) { return HttpContext.Current.User.IsInRole("DemoRole"); } Using HttpActionContext : protected override bool IsAuthorized(HttpActionContext actionContext) { return actionContext.RequestContext.Principal.IsInRole("DemoRole"); } 来源： https://stackoverflow.com/questions/28235979/web-api-2

问题 We are in the process of developing a in house mobile application and web api. We are using asp.net web api 2 with asp.net Identy 2 OAuth. I have got the api up and running and giving me a bearer token. However I want to slightly modify the process flow to something like along the lines of this: App user logs in to api with username and password. App receives Refresh-token which is valid for 30 days. App then requests an access token providing the api with the refresh token. ( Here I want to

问题 We are in the process of developing a in house mobile application and web api. We are using asp.net web api 2 with asp.net Identy 2 OAuth. I have got the api up and running and giving me a bearer token. However I want to slightly modify the process flow to something like along the lines of this: App user logs in to api with username and password. App receives Refresh-token which is valid for 30 days. App then requests an access token providing the api with the refresh token. ( Here I want to

问题 In the out of the box ASP.NET WEB API oAuth implementation after a new user calls: GET api/Account/ExternalLogins?returnUrl=%2F&generateState=true user is redirected to external log in (in my case Facebook) resulting in a token that they use for registration (out of the box code bellow) // POST api/Account/RegisterExternal [OverrideAuthentication] [HostAuthentication(DefaultAuthenticationTypes.ExternalBearer)] [Route("RegisterExternal")] public async Task<IHttpActionResult> RegisterExternal(

问题 In the out of the box ASP.NET WEB API oAuth implementation after a new user calls: GET api/Account/ExternalLogins?returnUrl=%2F&generateState=true user is redirected to external log in (in my case Facebook) resulting in a token that they use for registration (out of the box code bellow) // POST api/Account/RegisterExternal [OverrideAuthentication] [HostAuthentication(DefaultAuthenticationTypes.ExternalBearer)] [Route("RegisterExternal")] public async Task<IHttpActionResult> RegisterExternal(

问题 I'm implementing a Web API interface to support some fairly complex queries to run against it and have run up against an issue with the maximum request URI length. The definition of my Web API method looks like this (using Automapper to perform the DTO projections): public IQueryable<ReportModel> Get(ODataQueryOptions<Report> queryOptions) { var query = DbContext.Query<Report>(); return (queryOptions.ApplyTo(query) as IQueryable<Report>).WithTranslations().Project(MappingEngine).To