What SSO covers and what it does not
The described SSO covers entry from the qualification portal, where the person's identifier is passed in the id_token. This is a solution for contractors whose qualifications and permits are kept in the portal. It is not a feed of accounts from the plant's user directory.
The feature documentation does not describe feeding accounts from the user directory, so integration with a directory should be treated as a topic to be settled with IT, not as a standard. If the plant expects one directory for its own employees, the scope must be discussed before the offer, not during the rollout.
Stage 1: an access request and one decision role
An access request goes to the administrator, and accepting, rejecting and repeating a decision is limited to one administrative role. The plant's IT indicates who holds it and ensures a substitute for holidays and organizational changes.
Without an appointed person, requests wait in a queue and the contractor stands at the gate. Define a response time, for example within one shift, and check the queue every day during the first weeks.
Fields of the exchange log entry
Stage 2: do not link other people's accounts automatically
An account whose e-mail address already exists in the system is not linked automatically with the account from the portal. The proof of identity is a password or a badge, and the link is created at the first login. This rule protects against taking over an existing account by someone who knows only the e-mail address.
For IT this means that at the first login of a contractor with an existing address, an additional step must be planned and the helpdesk informed. The report I cannot log in through the portal is then usually a question about the first link.
- Check whether the contractor's e-mail address already exists in the system.
- Prepare the person to confirm identity with a password or a badge.
- Do not link accounts manually without proof of identity.
- Record the first link in the change register.
Stage 3: keys, settings and the exchange log
Integration keys never leave the browser, and the SSO panel shows settings read-only. Changing keys on the plant side is planned with the portal administrator and recorded in the IT change register.
The exchange log with the portal records direction, event, person, result, HTTP code and time. Writing to the log never interrupts the main operation, so the lack of a log entry does not mean that the operation failed. When analysing a problem, compare the log with the audit trail of changes.
Common pitfalls
The first is the assumption that SSO will serve all users of the plant, including the plant's own employees. The second is the lack of a named role that accepts requests. The third is the expectation of automatic linking of accounts by e-mail address, which the system deliberately blocks.
It is worth planning a test with one test contractor: a request, acceptance, first login and an entry in the log. Recording the result in the acceptance protocol closes the stage and provides evidence for an audit.
Video
Frequently asked questions
Does SSO feed accounts from the plant's user directory?
The documentation does not describe this. The described SSO covers entry from the qualification portal, and the user directory is a topic to be settled with IT.
What happens when the contractor's e-mail already exists in the system?
Accounts are not linked automatically. The proof of identity is a password or a badge, and the link is created at the first login.
Who decides on access requests?
One administrative role. The plant assigns it to named people and arranges substitutes.
Let's plan SSO from the portal together with IT
We will set the role that accepts requests, the rules for linking accounts and a test with a contractor before the first contractors enter the system.
Let's talk