Implementing Before Rule for SAP Business One (SAP B1) API Authentication in SailPoint IIQ

[IAMKhalid (Khalid Hussain)]

Which IIQ version are you inquiring about?

8.5

Share all details about your problem, including any error messages you may have received.

Hi,

I am currently integrating SAP Business One with SailPoint IIQ using the Web Service Connector.

We are working with the SAP Business One OData API and need to perform operations such as user creation, enabling, and disabling users. Each operation requires authentication first, after which a token is generated and must be included in subsequent requests (e.g., create, enable, disable).

Could you please advise on the best way to implement this in SailPoint IIQ? Should we use a Before Rule for handling authentication and token management, or is there a more suitable approach?

The login process requires the following attributes:

• CompanyDB

• Username

• Password

If anyone has reference materials, sample rules, or scripts for a similar implementation, it would be greatly appreciated.

Thank you.

[robert-hails]

Hi @IAMKhalid - have you explored the Custom Authentication endpoint to handle this behavior?

Believe this should meet your use case

Link to docs: Configuration for No / Custom Authentication

This post was answered by a Palyrian Solutions Architect. Feel free to message me directly if your problem requires a deeper dive.
palyrian.com | ‪(301) 284-8124‬

[r_pragati (Pragati Rastogi)]

Hi @IAMKhalid - You can use custom authentication like below screenshot.

Response will be stored as access_toekn.

In each operation, add a custom header “Authentication”. Its value would be "Bearer $application.token$."

Hope this helps!