InnerWeb
Skip to main content

Integration with the plant's user directory: guide for the IT department

The IT department often assumes that accounts in the occupational safety system will be fed from the plant's user directory. The feature documentation does not describe this, so the integration is agreed with IT as an option. This guide shows how to prepare the account list and what works today as SSO.

401
response to a missing or wrong machine token
Source: karta
8
maximum number of results in a search response
Source: karta

What is and is not part of the standard

The feature documentation does not describe feeding accounts from the plant's user directory. The described SSO covers entry from the qualification portal with a person identifier in the id_token. These are two different things: the first is synchronizing accounts from the plant's identity source, the second is a user entering the portal after they have already been authenticated there.

The conclusion for planning: directory integration should be treated as a topic to agree with IT, with its own scope, timing and pricing, not as an element of a standard installation. Until the scope is recorded, the schedule should not assume it.

Step 1: decide who is the source of truth about people

In a plant, people are often recorded in several places: in the user directory, in the HR system, in access control and in the qualification portal. IT indicates which source decides that a person exists and whether they are active. Without this decision the account list will drift apart within a few weeks.

A practical rule: one source for account activity and one for permissions in the occupational safety system. Record them in the implementation document together with the person responsible.

Search query limits in the portal API

Search query limits in the portal APIBar chart: minimum 3 characters in a query and maximum 8 results in a response02468characters or resultsMinimum characters in query: 3 characters or results3Minimum characters in queryMaximum results in response: 8 characters or results8Maximum results in response
Source: Component card: qualification portal integration documentation

Step 2: prepare the account list

The account list is a summary of the people who are to log in, with the minimum set of data needed to create them and assign roles. A well-prepared list limits personal data to what is needed and has one owner on the plant side.

An account whose email already exists in the system is not merged automatically with an account from the portal. The proof of identity is the password or the badge, and the link is created at the first login. It is worth warning users that the first login requires such confirmation.

  • The person and a unique identifier in the source of truth.
  • The role in the system and the place in the plant structure.
  • The activity status and the date when access expires.
  • Information whether the person uses a kiosk device.
  • The owner of the list on the plant side.

Step 3: SSO from the qualification portal

The API for the qualification portal requires a machine token in the header. A missing or wrong token returns response 401. Search queries require at least 3 letters or digits and return at most 8 results. Integration keys never reach the browser, and the SSO panel shows settings read-only.

When registration from a QR poster is enabled, the same token creates accounts and companies and issues passes. The risk assessment and the token rotation plan must take this into account. The exchange log records the direction, event, person, result, HTTP code and time, and writing to the log never interrupts the main operation.

Step 4: set the directory feeding option

If the plant wants to feed accounts from the directory, the arrangements cover: the format of source data, the feeding frequency, how accounts are deactivated, handling of people without an email, and how users log in on their side. We describe this as an option on request, with a scope agreed with IT before go-live.

Until these arrangements are made, accounts can be entered from a list prepared by the plant, and MFA can be enabled as an installation option. This path allows the system to start without waiting for the integration.

Evidence for the audit

For an audit it is enough to keep the decision on the source of truth, the account list with its date, the record of the integration scope and an extract from the exchange log. The audit trail covers entities changed by a person, so changes of permissions are visible in the record of changes.

Video

Frequently asked questions

Does the system synchronize accounts with the user directory by itself?

The feature documentation does not describe this. Feeding accounts from the directory is agreed with IT as an option on request, with a separate scope.

What about an account whose email already exists in the system?

It is not merged automatically with the account from the portal. The proof of identity is a password or badge, and the link is created at the first login.

Can the project start without directory integration?

Yes. Accounts are entered from a list prepared by the plant, and directory integration can be added later if the plant needs it.

Sources

Let's agree the account scope with your IT

We will go through the source of truth about people and the account list, and record whether you need feeding from the user directory.

Let's talk