28 apr

Session authentication


E-invoicing in Germany: How to implement the obligation with SAP Business One

Session authentication is an authentication method whereby a clients logs in to the server once with username and password and in return receives a time-limited session identifier — typically as a cookie. All subsequent requests pass this identifier instead of the actual access credentials; the server resolves the identifier server-side and thus knows the associated user.

Context

Of the Service Layer SAP Business One consistently works with session authentication. The login call POST /b1s/v2/Login with JSON payload {CompanyDatabase, UserName, Password} takes effect upon success B1 SESSION-Cookie; this will be sent with all further HTTP requests. Sessions expire after a configured period of inactivity and then return HTTP 401 responses — clients therefore need to implement an auto-relogin logic that intercepts 401, logs in again, and retries the original request. Advantages include simple integration (Only cookie management required, no token handling), clear assignment to a B1 company tenant and server-side revocability via Log out. The DI server uses comparable logic with its own SessionID; the SAP B1 Windows client also holds a session against the Company DB.

Demarcation

Session authentication is not a standard like OAuth 2.0 or OpenID Connect: it tightly couples the client and server, makes horizontal scaling and stateless APIs more complex, and is therefore less suitable for public APIs with many consumers. Tokens (JWT, Bearer) carry their validity and claims themselves, making them stateless. Compared to Basic Authentication Is session authentication more secure because credentials are not sent with every request — with the caveat that the cookie itself must be protected (HTTPS, HttpOnly, Safe, SameSite).


ReAct and RLEF

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...
Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
RLHF

RLHF and reward models: AI hype or what the approval process in SAP Business One has to do with it

Key takeaways: The article covers the application of artificial intelligence in the context of SAP Business One and fundamental AI topics. Thanks to ...
AI Webinar

AI – Answers from SAP Business One – without SQL, without IT ticket

Live webinar on 30 July 2026, 14:00–14:30 | Live demo via Microsoft Teams | Duration: 30 minutes „How were the sales...".
Wird geladen …