28 apr

Session authentication

Versino Financial Suite

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).


AI in everyday work: Person starts with their own task instead of the learning pile

AI in everyday work: Here's how to find the right start

Anyone who wants to use AI in their daily work is familiar with this: You read an article about prompts. A new model appears in it ...
AI-SHOP

AI assistant meets SAP Business One: Two paths out of the Versino AI shop

AI assistants like Claude or Copilot write emails, compile documents, and explain technical terms. But when you ask them about the open-source code...
SPRINT & SWIRL

Sprint and Swirl: How an AI agent divides work and learns from trials

This series deals with artificial intelligence in conjunction with SAP Business One. It takes a close look at fundamental AI principles...
LATS

LATS: Considering several paths simultaneously with AI — and the availability check in SAP B1

This series focuses on artificial intelligence in conjunction with SAP Business One. Not as a collection of product announcements, but as...
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 ...
Wird geladen …