talend does not work

by Jannik Arndt

I cannot believe that googleing “talend does not work” does not find anything helpful. With this entry I try to fill that void in the internet.

Fail 1: Download

You can download talend on their website — except you can’t. After filling out all the information (pro-tip: store them in LastPass to insert them the next couple of times) you have to accept the terms of use—except you can’t!

There is no event listener. What the…?

There’s a trick: Select the “Phone”-field and alt + tab until you arrive at the checkbox, then hit space.

Next: Enjoy your modern webbrowser prohibiting a site to cross-reference http from https

But there is a download-link hidden inside the plethora of error messages:

If you’re looking for these, here you go:


They won’t help you, because they might be offline. If not, you get one of the greatest tools of all times—not.

Fail 2: The Download-Tool

Pretty simple: You start it, it does nothing:

Reminds me of “A Sharepoint that does throw errors is a good Sharepoint”.

Fail 3: The ZIP-File

Okay, while you wait for the download tool to do anything, you can also try out the ZIP-download-option. This link surprisingly worked! And it contains a Talend-Studio-macosx-cocoa.app file!

An unsigned one, of course, because why make things easy? The common advise you find on the internet is to turn off Gatekeeper, Apples system tool to prevent you from running malicious code (i.e. from developers who do not pay apple 100$/year). The easy way to get around this is to right-click a file and then click open. One would suspect this to do the exact same thing as double clicking the file, but watch and learn: It gives you an extra button:

And the next thing you see is: “The Talend-Studio-macosx-cocoa executable launcher was unable to locate its companion share library”.


This is a hard one: You need to right-click the app, choose Show package contents, navigate to Contents:MacOS:Talend-Studio-macosx-cocoa and execute that. Voilà! It starts!


I recently created a wonderful bug.

This is a basic example how to implement oAuth2 using Akka HTTP and Scala. It provides three endpoints. From the clients point of view:

  • / — publicly accessible, returns “Welcome!”,
  • /auth — provide your username and password, receive an access_token in return,
  • /api — secured by oAuth, send the access_token in a header to gain access.

From the server’s point of view:

  • / — publicly accessible, do nothing,
  • /auth — receive basic auth credentials, verify they’re in the list of known credentials, create an access_token, return it,
  • /api — receive authorization header, check if access_token is in list of valid tokens.

Since oAuth tokens are short lived, the server also has to invalidate expired tokens.

Getting a Akka HTTP-based backend up and running on Heroku for free can be done in less then 30 minutes — if you know the tricks.