I had a look at this with Zhi Qiang.
With a quick curl test we can see that the url will present a 400 code if any basic auth header is used, but if no basic auth header is used, then it comes back fine. I have to believe that what's happening here is that ACE is still sending the basic auth header even if you set the username and password to empty strings.
The documentation says this:
If the endpoint requires no authentication, specify a blank username and password in JSON format in a text editor:
{"authType":"BASIC_AUTH","credentials":{"username":"","password":""}}
Can anyone confirm the behaviour?
------------------------------
James Hewitt
------------------------------
Original Message:
Sent: Thu August 25, 2022 11:21 AM
From: ZHI QIANG KOU
Subject: Help! Failed to run IntegrationServers using bar files stored in external endpoints
Hello everyone,
This is urgent question from our customer. Please help!
I have APP Connect operator installed on OCP platform. And I want to run IntegrationServers using bar files stored in external repository.
The procedure I am following is this:
https://community.ibm.com/community/user/integration/blogs/rob-convery1/2021/06/25/acecc-bars-from-external-endpoints
The blog says to connect to an endpoint that does not have basic authentication enabled, we should supply a blank username and password likes this: {"authType":"BASIC_AUTH","credentials":{"username":"","password":""}}
I have created barauth type configuration successfully. And the corresponding secret is created as well by operator.
But I failed to create Integration Server with this barauth type configuration. The error message is: admission webhook "validate.barendpoints.appconnect.ibm.com" denied the request: BarURL - Non-OK HTTP status returned: 400, please check the credentials provided in your barauth configuration
Any comments is appreciated.
Regards,
Eric
------------------------------
ZHI QIANG KOU
------------------------------