c# asp.net Web API Owin Json Token

Question

Hey I just programmed a token based authentication following this tutorial. So everything goes fine as long I send my POST request as x-www-form-urlencoded. So now my teammate needs to get the token with a json, but all he gets is "unsupported grant_type". So can I change the acceptable type for the token or do I have to find another solution?

My configuration looks like this:

public void Configuration(IAppBuilder app)
    {
        app.UseCors(Microsoft.Owin.Cors.CorsOptions.AllowAll);
        var myProvider = new MyAuthorizationServerProvider();
        OAuthAuthorizationServerOptions options = new OAuthAuthorizationServerOptions
        {
            AllowInsecureHttp = true,
            TokenEndpointPath = new PathString("/token"),
            AccessTokenExpireTimeSpan = TimeSpan.FromDays(1),
            Provider = myProvider
        };

        app.UseOAuthAuthorizationServer(options);
        app.UseOAuthBearerAuthentication(new OAuthBearerAuthenticationOptions());

        HttpConfiguration config = new HttpConfiguration();
        WebApiConfig.Register(config);
        }
    }

This is how my request look like keep in mind this doesnt work with json And with a JSON it doesnt work: Best regards :)

are you sending grant_type as password in your request..?? — Vivek Singh
– Vivek Singh, Commented Feb 28, 2017 at 10:59
added a picture of my request in my question. Is it right so? — Johannes Gnadlinger
– Johannes Gnadlinger, Commented Feb 28, 2017 at 15:19
Yes it's correct...now use the access_token in your your header authenticate your API request... — Vivek Singh
– Vivek Singh, Commented Feb 28, 2017 at 16:04
Eg: Authorization : bearer access_token...in the header of postman — Vivek Singh
– Vivek Singh, Commented Feb 28, 2017 at 16:06
yeah I already got this but the problem is that this only works with x-www-form-urlencoded and not with JSON — Johannes Gnadlinger
– Johannes Gnadlinger, Commented Feb 28, 2017 at 16:07

Vivek Singh · Accepted Answer · 2017-02-28 17:02:17Z

3

The reason behind the use of application/x-www-form-urlencoded as Content-Type is simple: the OAuth2 specification (RFC 6749) requires this content type for token requests.

Any other content-type will break OAuth2 compliant clients compatibility. I advice you to not change this standard behavior.

The default implementation of OAuthAuthorizationServerMiddleware (more precisely the internally used OAuthAuthorizationServerHandler) from Microsoft.Owin.Security.OAuth just ignores the Content-Type header and tries to read the request body as a form anyway.

For Another way , In RequestBody you can write, grant_type=password&username=yourUserName&password=MyPassword123,

Also make sure after grant_type=password&username=username&password=password there is no space or line break.

edited Feb 28, 2017 at 17:02

answered Feb 28, 2017 at 16:49

Vivek Singh

1,11310 silver badges20 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Johannes Gnadlinger Over a year ago

yeah worked for me now... sorry that it took me so long^^

Collectives™ on Stack Overflow

c# asp.net Web API Owin Json Token

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related