Matt Sicker

Going to have to redo the relevant changes from here as I've included some of these changes in a different PR.

This could end up there, yeah.

> @jvz is this meant to be an issue in https://github.com/apache/logging-log4j-kotlin ? Good idea. Transferred.

Yes, I like this idea. Once that is in place, we can even implement some minimal multi-platform implementations (e.g., there's a common `println` and `readln` function for all platforms), and...

By the way, I've since migrated to doing it all in-gradle, but this feature is still useful for users migrating from the maven karaf plugin.

Do you have Xcode installed? That's usually required.

I'm not sure on the exact config here, but it sounds like you need to add your LDAP username to a config file for authentication.

References: * https://docs.spring.io/spring-security/reference/5.7/servlet/architecture.html#servlet-exceptiontranslationfilter * https://docs.spring.io/spring-security/site/docs/5.7.9/api/org/springframework/security/web/access/ExceptionTranslationFilter.html And you still store the `RetrofitError` in the `cause` of the exception.

That sounds like a good long term solution, but swapping out the backend for service proxies seems like a more risky change.

Retrofit -> Retrofit 2. While that's separate from the HTTP backend, it's still part of the service proxy middleware.