AspNet core 401 - No SecurityTokenValidator when adding the token

Question

For a Jwt token:

HttpResponseMessage responseMsg var token = responseMsg.Content? .ReadAsStringAsync() .GetAwaiter() .GetResult();

Used to authorize a post request, like this:

client.BaseAddress = new Uri("https://..."); client.DefaultRequestHeaders.Accept.Clear(); client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json")); client.DefaultRequestHeaders.Add("Authorization", $"Bearer {token}");

I'm getting this error:

Bearer was not authenticated. Failure message: No SecurityTokenValidator available for token: "eyJ..."

After a closer look to the request in postman I discovered that the issue are the "" added to the token on the header:

That is why I add the token like this:

client.DefaultRequestHeaders.Add("Authorization", $"Bearer {token.Replace("\"", "")}");

And this works, but it seems "dirty" to me. Is there a better way?

could you share more about the creation of the token, it seems that you are retrieving it out of the scope of the code shared — Juanito
– Juanito, Commented Dec 3, 2019 at 11:59

DanielV · Accepted Answer · 2019-12-03 12:51:33Z

You should deserialize the response object so that you can use it as a string:

HttpResponseMessage responseMsg var response = responseMsg.Content? .ReadAsStringAsync() .GetAwaiter() .GetResult(); var token = JsonConvert.DeserializeObject<string>(response); return token;

Now the string is ready to be included in the header as a bearer token.

Collectives™ on Stack Overflow

AspNet core 401 - No SecurityTokenValidator when adding the token

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related