InnerWeb
Skip to main content

Integration service account and permissions: recommendations

An integrator who collects data from the system should not use an employee account. A technical account with a clearly limited scope is safer, easier to audit and does not disappear when a person leaves. Below are six recommendations for the IT department and the application administrator, based on how machine tokens work in InnerWeb integrations.

4
response codes of the access request interface
Source: karta
30 dni
expiring status window for trainings
Source: karta

Why not an employee account

An employee account is tied to a person: their role, password, second login factor and employment cycle. An integration based on such an account stops working on the day the employee leaves or changes the password, and in the event log it is hard to tell a human's action from an automated one.

A technical account solves all three problems at once. It has an owner on the IT side, a limited scope and its own trace in the log. InnerWeb integrations (the Person API, access requests and the webhook poller) use machine tokens, so they naturally support this model.

Recommendations 1 to 3: scope and separation

The first three recommendations concern what the account may do and what it is for.

1. One account per integration

The webhook poller, the access request portal and the Person API should each have separate credentials. Leaking or rotating one token does not stop the other integrations, and the log clearly shows which integration made a call.

2. The smallest possible scope

The poller needs only to fetch pending entries and confirm deliveries, nothing more. The request portal sends requests and receives decisions. Data on permissions, trainings and medical checks is accepted only when the scope of consent covers it, so the scope should follow the person's consent, not the integrator's convenience.

3. Separate the integration account from the decision role

Accepting, rejecting and retrying a decision in access requests is available only to the service administrator role; the panel is also visible to the administrator and to occupational safety staff. The technical account should not carry this role. Access decisions stay with a human.

Recommendations 4 to 6: lifecycle and supervision

Recommendation four: appoint an owner of the account on the plant's IT side. The owner decides on rotation, retirement and a review of the scope once a year or when the integrator changes. An account without an owner is the most common cause of forgotten access.

Recommendation five: plan the response to response codes. An access request is accepted through the interface with a machine token and returns 201 for a new request, 200 for a repeat of the same identifier, 400 for invalid data and 401 for a missing or wrong token. The integrator should raise an alarm when a series of 401 codes appears, because it means an expired or revoked token. An account deleted in the Person API returns 404.

Recommendation six: do not move keys into a browser or into administrators' scripts. In the SSO panel the settings are read-only, and keys never reach the browser. The same pattern applies on the integrator's side: credentials go in a secrets manager, not in a file on the desktop.

How to hand over the account to an integrator properly

The handover should take the form of a short protocol: the name of the integration, the scope, the owner on the IT side, the date of the review and the retirement procedure. This way, once the project ends, the integrator does not keep access for an indefinite period.

When accepting the work, check in the exchange log that the calls have the expected direction, result and HTTP code. The log records exchange events, and writing to it never throws an exception, so a log failure will not stop the integration, but it is worth reviewing regularly.

Video

Frequently asked questions

Can the technical account accept access requests?

It should not. Accepting, rejecting and retrying a decision is available only to the service administrator role. Access decisions stay with a human.

What does a series of 401 responses mean?

A missing or wrong token. Most often it has expired or been revoked, so the integrator should report it to the account owner.

How often should the account scope be reviewed?

Once a year, and whenever the integrator or the scope of the integration changes.

A safe handover of the integration

Ask us for a template of the technical account handover protocol and the scope list for your integration.

Let's talk