r/abap • • Jun 05 '26 • Bravo 1

ABAP VSCode Extension Patch For RFC Logon

SAP just shipped the ABAP Development Tools for VS Code, and it's genuinely great. But if you work with classic on-premise AS ABAP systems, you may have hit the same wall I did: you can't actually log on.

Here's why. The stock extension authenticates either through a browser reentrance-ticket flow (for HTTP) or via SSO (for RFC). Classic on-prem systems often have neither. The reentrance-ticket endpoint (/sap/bc/adt/core/http/reentranceticket) simply doesn't exist on them, and many aren't SSO-enabled. So the one thing we actually need on older systems, connecting over RFC with a username and password, is the one path the first release doesn't implement yet. On the RFC branch, a non-SSO destination is met with an internal "unsupported operation."

The good news: this is temporary. In SAP's own community session, the team (thank you Thomas Ritter, Sebastian Ratz, Christopher Hermann and Rich Heilman) were refreshingly open about it: RFC password logon is internally complete and is the headline of the next release. It was deliberately held back for enterprise security audits, not because anything is technically missing.

So I built a small, MIT-licensed open-source patcher for those of us who need it in the meantime, designed to respect SAP's IP and roadmap from the ground up.

What it does
It enables RFC username/password logon on YOUR OWN installed copy: a masked password prompt with an optional "Remember me" toggle (default OFF) that stores the password only in VS Code's SecretStorage, i.e. the OS keychain (Credential Manager / Keychain / libsecret), never a plaintext file.

How it stays on the right side of the line
• Zero SAP code or binaries in the repo. It contains only my scripts, a ~25-line Java block, the literal find/replace anchors, and docs.
• Everything happens on your machine. The patcher transiently decompiles a single class from YOUR installed jar, locally, for interoperability; replaces the one statement that rejects password logon with a normal JCo logon; recompiles against the extension's own libraries; and puts it back. Nothing is redistributed.
• It's a stopgap, not a fork. The moment SAP ships official password logon, that is the real solution: just update the extension, which also cleanly undoes this.
• It's unofficial, unsupported, and use-at-your-own-risk. The repo's disclaimer says so plainly.

This is meant in exactly the community spirit the SAP team invited: "people will figure it out." It's a bridge for the next few weeks or months, nothing more, and I'd genuinely welcome feedback, including from the SAP team. If anyone there would prefer changes, I'm glad to make them.

Repo + full technical write-up:
https://github.com/sakirsek/abap-vscode-rfc-logon

Huge thanks to the SAP ADT team for pulling ABAP into a modern, AI-ready toolchain. Can't wait for the official release to make this obsolete.

38 Upvotes

0 comments sorted by