Skip to Content
Technical Articles
Author's profile photo Morten Wittrock

CPILint version 1.0.2 is out

CPILint%20logo

Yesterday, I released CPILint version 1.0.2:

CPILint%20console%20output%20showing%20version%20number

CPILint is an open source, command-line tool for SAP Cloud Integration, which lets you automate the governance of your integration flows by writing executable, rule-based development guidelines.

CPILint ships with a number of built-in rules, covering adapters, mapping, scripting, security and more. Once you’ve chosen the rules that make sense in your particular situation, CPILint does the heavy lifting of checking your integration flows for compliance, and presents you with a report of the issues discovered.

If this is the first time your hear about CPILint, please read this blog post for a much more in-depth introduction.

So what’s new in version 1.0.2? First and foremost, this release updates the tool to use the public integration packages API. Version 1.0.1 still used the undocumented API, which no longer works.

1.0.2 also introduces the CPILINT_JAVA_HOME environment variable, which you can use to launch CPILint with a specific Java runtime. Also, the Bash launch script now works correctly on macOS.

You can download CPILint version 1.0.2 from GitHub. If you want to tinker, the full source code and all other files needed to build CPILint is included in the download. Everything you need is available in the CPILint GitHub repository as well, of course. For documentation and installation instructions, please see the project’s wiki.

Have fun with CPILint! If you run into any issues at all, do please let me know. You can do that by either commenting below, or by creating an issue on GitHub.

Assigned Tags

      6 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Michael Kühn
      Michael Kühn

      Hi Morten,

      Thanks for sharing this great tool. Do you support also custom identity providers (e.g. SAP IAS)?

      Unfortunately it doesn't work for us...

      Best regards,
      Michael

      Author's profile photo Morten Wittrock
      Morten Wittrock
      Blog Post Author

      Hi Michael

      The credentials are used for the OData API calls, and I believe you should still use your SAP ID Service user for that, but let me check and get back to you.

      Regards,

      Morten

      P.S. Also make sure that you are actually hitting the correct Tenant Management Node hostname.

      Author's profile photo Michael Kühn
      Michael Kühn

      Hi Morten,

      Thanks a lot for the fast response. For our tenants also basic authentication is "redirected" to our custom IdP. I verified the basic authentication against one of the odata API endpoints.

      Our error message looked like this:
      screenshot

      Finally I solved it by using another client (outside company network). I guess the internet proxy was causing the issues.

      Thank you again for sharing this great tool!

      Best regards,
      Michael

      Author's profile photo Morten Wittrock
      Morten Wittrock
      Blog Post Author

      Happy to hear it worked out 😀

      Author's profile photo Michael Kühn
      Michael Kühn

      Just to share our experience on API authorization with custom IdP: We also faced further authorization issues in Neo environment when using a custom IdP in combination with group mapping between BTP authorization groups and LDAP groups (caused by CPI API). Finally we solved it by manually assigning the technical user ID of IAS (e.g. P000xxx) to the BTP developer group. LDAP username was not working for API authorization (even if automatically mapped to BTP group before & working in CPI environment).

      Author's profile photo Morten Wittrock
      Morten Wittrock
      Blog Post Author

      Hi Michael

      That's useful - thanks for sharing!

      Regards,

      Morten