× 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.



If you're using GETURI it will do this automatically for BASIC
authentication.

You would set AUTHUSER to the application ID, and AUTHPW to the shared
secret and it will automatically use the colon and base64 encode it.

It's basically the same as when using a user and pw for basic
authentication.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #19 <https://www.bvstools.com/mailtool.html>: The ability
to turn off "Strict SSL" settings. This means no importing Certificate
Authorities (CAs) unless you want to.

On Mon, Jun 3, 2019 at 3:45 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

This is less RPG-related, and more HTTP-related (I am not a web
programmer).

I'm working with a new API (as a consumer). Their documentation states
that the Authorization part of the header should be:

Authorization Basic MTIzNDU6YWJjZGU=

The characters after basic represent "The application ID and shared secret
must be concatenated using a colon then RFC2045-MIME (base-64) encoded."
(in this case 12345:abcde)

So I did the concatenation and base64_encode in my program BEFORE using
the HTTP_SETAUTH procedure of HTTPAPI. After reviewing the debug.txt file,
I could clearly see that HTTP_SETAUTH does that for me (I was basically
encoding the "user" and "password" only to have HTTP_SETAUTH do it again)

This code works just fine:
rc = http_setauth(HTTP_AUTH_BASIC : applicationID : sharedSecret);

I would just like to understand how http_setauth "knows" to encode these.
Is that an HTTP/HTTPS standard?


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.