Sending parameters by get method to rest api

ali-aydin

@mchinand
Bearer must be added to the token.
in postman there is no header
in authorization tab
only added token and in parameters tab is only one parameter :KalaCode
in body tab username,password and grant_type
in the qt when I want to authenticate by

QUrl url("http://localhost:594444/api/authenticate");

it returns "Hello"
but when i changing url to

QUrl url("http://localhost:594444/api/Getmojodi" );

it does not work

mchinand

I meant the 'Headers' tab of the Postman request:

The authorization header value above was automatically set when I added a (junk) username and password in the Auth tab:

ali-aydin

@mchinand
there is no problem in postman
problem is that how can we do authorization in qt?
i think yhe main problem is this

mchinand

Are you setting the Authorization the same in Qt as the value it is set in Postman? Your variables are 'basic_authorization' and 'token', is token just the token or is the token type prepended to it ('Basic ' or 'Bearer ')? Your variable is 'basic_authorization' but in your prior message, you mention adding 'Bearer' before the token, which auth method are you using?

ali-aydin

@mchinand
i'm using url.setRawHeader() for add token to url and
and adding bearer to token
i don't use any auth method
how to use that?

mchinand

Are you doing Basic (username/password) or Bearer Token? What method are you selecting in Postman? What is the value of your token variable, post the string but modify the actual token part.

ali-aydin

@mchinand
in postman i selected bearer method
and token has three part access_ token,token_type and expire_date
in qt i added "bearer" to access_token then adding this token to url.setRawHeader()

mchinand

What is the value of your token variable, post the string but modify the actual token part.

ali-aydin

@mchinand
this is token file

{
   "access_token": "1zVIXlpahfvS82xJEN2l2L7vPaUvX-AqHD5w_JmrSqHtV_hHdk6dKqdyFx6D62p1jPIcPPMdlVlsOlS4ZcoVUcsnrzTv8Ly42OLINofJYfdkVoitAQGdCzX7vYlnWBYNrxAOsMJiCdbjvONC2MftONA_hxhcsf8D3ax24buIupEkqPUoaBWUd6nx7HTx3Axo8ZdHZhM48SS68CczY-EDVUTDQSvYxv_4gQCxf_uWPuTrjTF2jwCbLfrCmhK7O_WJ07XmV-PYTj2jV7E35CpeFtx6W_FePFlhzim9qLv",
   "token_type": "bearer",
   "expires_in": 86399
}

mchinand

Try

QString token = <access_token from file>
token.prepend("Bearer ");
req1.setRawHeader(QByteArrayLiteral("Authorization"), token.toUtf8());

I don't think you want the 'toBase64()' that you have in your code above.

ali-aydin

@mchinand
nop it is not ok

SGaist

Check the request sent by postman and the one from your application and compare for differences.

ali-aydin

@SGaist
yes good idea

mchinand

Be sure to compare the url, body, and header (also, be sure to look at the auto-generated headers in Postman which are hidden by default). Are you extracting the token correctly from your file? Have you debugged that part of your code? You did not include that with your original post.

ali-aydin

@mchinand
error body is :
Error transferring http://localhost:59444/api/Getmojodi?KalaCode=20101010131310 - server replied: Forbidden
and ststus code is :403
and hidden headers in postman :

ali-aydin

@mchinand
@JonB
@SGaist
@Axel-Spoerl
Thank you everyone without your help I could not resolve that.
Thank you so much

ali-aydin

@ali-aydin
this problem solution :
request must be in this shape :

QUrl url("http://localhost:59444/api/Getmojodi");
    
    request.setRawHeader(QByteArrayLiteral("Authorization"),token.toUtf8());
    request.setRawHeader("Content-Type", "application/x-www-form-urlencoded");
    request.setRawHeader(QByteArrayLiteral("User-Agent"),"ApiTest2/1.0");
    request.setRawHeader(QByteArrayLiteral("Accept"),"*/*");
    request.setRawHeader(QByteArrayLiteral("Accept-Encoding"),"gzip, deflate, br");
    request.setRawHeader(QByteArrayLiteral("Connection"),"keep-alive");
    request.setSslConfiguration(QSslConfiguration::defaultConfiguration());
    QUrlQuery uq;
    uq.addQueryItem("KalaCode","20101010131310");
    url.setQuery(uq);
    request.setUrl(url);
    manager->get(request);

SGaist

The user agent is likely not needed in your case.

I think that you essentially need Content-Type and Accept-Encoding beside Authorization.

ali-aydin

@SGaist
Thank you I will check it