Comments by MrJay994 (Top 8 by date)

Yes, I agree, as you can see I tried doing that in the client with the try catch block

try {
Poco::Net::initializeSSL();
Poco::Net::HTTPSClientSession session(uri.getHost(), uri.getPort(), context);
std::ostream& myOStream = session.sendRequest(req);
object1.stringify(myOStream);

// get response
Poco::Net::HTTPResponse res;
session.receiveResponse(res);
std::cout << "Response Status = " << res.getStatus() << std::endl;
std::cout << "Response Reason = " << res.getReason() << std::endl;

Poco::Net::uninitializeSSL();
} catch (const Poco::Net::SSLException& ex) {
std::cerr << "SSL Exception: " << ex.what() << std::endl;
}

with std::cerr << "SSL Exception: " << ex.what() << std::endl; in the catch block

But appareantly only SSL Exception: SSL Exception is being provided :(.

Yeah, I'm pretty sure you yourself wouldn't manage to create an application using only these things among the search I also did on the internet and with what I found, this is why I asked perhaps for more. Have a good day

https://docs.pocoproject.org/current/package-Net.OAuth.html

These are all documentations.

https://www.ibm.com/docs/en/api-connect/5.0.x?topic=endpoint-tutorial-securing-api-by-using-oauth-20

This one is specific for the IBM application. I do now work with IBM.

https://docs.pocoproject.org/current/Poco.Net.OAuth20Credentials.html

This one is mostly documentation from which I can gather very little applicability.