↓ Skip to main content
retgits.com
How To Add Basic Auth To Flogo Apps in TIBCO Cloud Integration
  1. Blog/

How To Add Basic Auth To Flogo Apps in TIBCO Cloud Integration

·1 min·
TIBCO

I’ve gotten a lot of questions about using Basic Authentication with the Web Integrator in TIBCO Cloud Integration. Turns out it’s pretty straightforward.

When you’re using an InvokeRESTService activity in Web Integrator the tab Input Settings has section called Request Headers and in that table you can specify the HTTP headers you want to use. To add a header parameter, click the + button and press Enter to save your changes. For HTTP Basic Authentication you need to specify the header Authorization.

HTTP Basic Authentication passes the word Basic: (and a space) followed by a Base64-encoded string of the username and password. For example, Basic: dXNlcjpwYXNz is the value you’d use if the username/password was user:pass. In Web Integrator you can build this expression using the mapper. The expression on the Input tab for the above scenario would be string.concat("Basic: ", string.stringToBase64("user:pass"))

If you want to verify what headers your request is actually sending, RequestBin is a handy tool. RequestBin is a community project from Runscope that lets you inspect HTTP requests and debug webhook payloads. You can also host RequestBin yourself following the steps on GitHub.

Related

Monitoring Node.js Apps with Prometheus

·6 mins
TIBCO
In the age of monolithic apps and app servers, monitoring was relatively straightforward. With microservices, you’re dealing with more servers and more services, and monitoring gets complex fast. You have options — Nagios, Zabbix, or Prometheus. My preference goes to the Greek deity that stole fire from Mount Olympus and brought it to us.

How To Combine APIs With Flogo Apps In TIBCO Cloud Integration

·4 mins
TIBCO
In 2002 Jeff Bezos issued a mandate that would change the world forever. At the very least it brought a massive change to how data is reused on the Internet: All teams will henceforth expose their data and functionality through service interfaces. Teams must communicate with each other through these interfaces. There will be no other form of inter-process communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network. It doesn’t matter what technology they use. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. Anyone who doesn’t do this will be fired. Thank you; have a nice day! That mandate kicked off a lot of what we now call the API economy. Many enterprises have APIs that deliver data so you can focus on building value rather than figuring out how to get the data. That said, most APIs out there are documented but don’t have a swagger.json you can import directly. The Web Integrator in TIBCO Cloud Integration lets you paste sample messages from API docs and use those as the basis for invoking REST APIs.