OCI – Configure Login

In the General tab, under "Login", all settings are listed that determine how the procurement system starts the punchout session.

HTTP Request Method

Option	Description
GET & POST	Both methods are accepted (default, recommended)
GET	Only GET requests allowed
POST	Only POST requests allowed

Variable Names

The procurement system passes user data and the return URL as URL parameters or POST body. The field names are defined in the OCI standard but may differ between systems.

Variable name	Default	Description
User variable name	USERNAME	Parameter name for email address or username
Password variable name	PASSWORD	Parameter name for the password
URL variable name	HOOK_URL	Parameter name for the return URL
Token variable name	TOKEN	Parameter name for a token (alternative to password)

Example

A SAP system may send ~username instead of USERNAME.

Token Authentication

As an alternative to a password, a token can be used. The token is stored in a Shopware custom field on the customer profile.

Field	Description
Token variable name	Parameter name that the procurement system uses for the token
Token custom field	Technical name of the Shopware custom field on the customer profile where the token is stored

On login, the connector compares the submitted token with the value in the custom field of the matching Shopware customer.

Additional Options

Option	Default	Description
Validate URL	on	Checks whether HOOK_URL is a valid HTTP/HTTPS URL. Turn off if the system passes a non-HTTP URL (e.g. SAPEVENT:POST for SAP).
Guest session	on	The customer is logged in as an isolated guest session. They have their own cart but receive all customer-specific prices and discounts. Turn off if the customer should be logged in to their regular session.

Example Login URL (GET)

https://shop.example.com/AgiqonOciEntry/login
  ?USERNAME=buyer@company.com
  &PASSWORD=secret
  &HOOK_URL=https://procurement.company.com/oci/return

Example with Token

https://shop.example.com/AgiqonOciEntry/login
  ?TOKEN=abc123xyz
  &HOOK_URL=https://procurement.company.com/oci/return

Common Issues

Login fails — "URL validation"
If the procurement system passes a non-HTTP URL as the hook URL (e.g. SAPEVENT:POST), disable the Validate URL option.

Customer cannot log in

• Is the customer assigned to the system in the Customers tab?
• Is the system set to Active?
• Is the license key valid?
• Do the variable names match (e.g. ~username instead of USERNAME)?