|
On Oct 8, 2024, at 6:04 PM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:
Jay,
If you solved the "self-signed" problem by installing your certificate authority into your PC, please be aware that you've only solved the problem for yourself. In a production application, you should not be creating/signing your own certificates, you should be getting them from a registered/trusted certificate authority.
As for the 401 error -- it means that the site requires authorization. Some sites require "basic" auth (i.e. userid/password) others require a bearer token, etc. You need to configure PostMan to send the appropriate credentials.
If you are running the site and weren't expecting this requirement, then you need to look at your configuration (if Apache, that would be httpd.conf) and see where you having something like "Require valid-user". This could also be caused by providing the wrong URL (i.e. connecting to a different site that does require credentials.) If it's a 3rd party site, you need to look at their documentation.
But 401 means credentials of some kind are required, and you haven't provided them. Or that you have, and the ones you've provided aren't valid.
On 10/8/24 4:06 PM, Jay Vaughn wrote:--
Ok, I am beyond this now and getting a 401 auth error - not authorized...
I am not using user level security so QTMHHTTP is connecting to apache...
I can see a log in the access log that the request comes through...
I have granted QTMHHTTP to the lib and pgm in which i'm trying to execute.
where could the auth error be coming from?
Also I even recompiled my pgm I'm ultimately wanting to execute on the IBM
i and when I try the last used date is not being set so it has to be
something before that?
thanks
Jay
On Tue, Oct 8, 2024 at 4:15 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:
It’s actually the certificate.
It has been sone time since I’ve done this and it had worked before.
This time I’m running into this.
Thx
Jay
On Oct 8, 2024, at 3:45 PM, Brad Stone <bvstone@xxxxxxxxx> wrote:wrote:
I believe you need to export the (certificate authority) CA chain and
import in Postman or your PC.
On Tue, Oct 8, 2024 at 2:36 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
Error:we created an http appach application and created a new cert for it.
We were sure to specify the common name to match the name of the server.
In our http config we specify certificate required.
we export the .pfx and use this in postman under certificates...
However when we consume from postman we are getting an error... SSL
listSelf signed certificate in certificate chain... and in our http log we
get....
Improperly formated certificate or certificate not valid, error = 415
What are we needing to do to resolve this?
thanks
Jay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
relatedTo post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
listquestions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.