×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
OK more googling and I think this is starting to make sense.
The user name and password are converted to base64 and the used in the
authorization string in the header.
I will test and see if this works.
Don Brown
From: "Don Brown" <DBrown@xxxxxxxxxx>
To: "web400 (web400@xxxxxxxxxxxxxxxxxx)" <web400@xxxxxxxxxxxxxxxxxx>,
ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Date: 13/07/2019 01:04 PM
Subject: [WEB400] Basic authentication to web service and Postman
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>
I am hoping someone can assist/advise as I am a little puzzled
We are working on a new project and using Postman to test web service
calls and then this will be coded in RPG and use HTTPAPI.
In Postman we have set up the Authorization as "Basic Auth" and specified
the values for User name and Password
When we "Send" the Get request it work ... Great! But then looking at
the generated HTTP I am confused as it appears the basic authorization has
been converted to an authorization string
Can anyone advise how this conversion is done or why I am not seeing a
User name and Password details in the header ?
______________________________________________________________________
This email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email, MSD
cannot accept responsibility for any loss or damage arising from the use
of this email or attachments.
______________________________________________________________________
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.