What the SSO panel shows
The SSO panel in the permissions module shows the status of the integration, the number of active passes, the number of linked accounts, the requests waiting for a decision and the errors from the last 7 days. Next to it is the exchange log with the direction, the result and the HTTP code of each event. The settings are read-only, and keys never reach the browser.
For the security department this is a daily working screen: the number of requests waiting for a decision shows the backlog, and the number of errors from the last 7 days shows the health of the integration with the portal.
Who may decide
Accepting, rejecting and retrying a decision on access requests is available only to the service administrator role. The administrator and occupational safety staff can see the panel, but they cannot settle requests in it. The rollout should therefore start with an organisational decision: who in the plant holds the service administrator role and who covers for them during leave.
A typical mistake is assuming that because occupational safety can see the panel, it can also decide. A person from occupational safety, who is obliged to give an opinion on requests, should work in pairs with the service administrator, and the opinion must be recorded outside the panel, for example in an agreed internal form.
Response codes of the access request interface
How a request arrives
A request reaches the plant through the interface with a machine token. A response 201 means a new request, 200 a repeat of the same identifier, 400 invalid data, and 401 a missing or wrong token. Data on permissions, trainings and medical checks is accepted only when the scope of consent covers it, so a request without consent to trainings contains no training data.
When accepting the rollout, check that a repeat of a request returns 200 and not a second row in the panel. This is a simple piece of evidence that the plant side is idempotent.
E-mail address collision: the most important pitfall
When the e-mail address from a request already exists in the plant, the accounts are not linked automatically. The person receives a decision with a request to log in with the portal account and confirm with a password, and the panel warns the operator. This is a safeguard against someone taking over an existing account who knows only the e-mail address.
For the security department this means two things. First, the warning in the panel is not an integration error but a signal for caution: before a request is accepted, you have to assess whether the person really owns the address. Second, the procedure has to allow for contact with a person who cannot confirm the password, for example because they forgot their accounts after a change of job.
An undelivered decision and retrying it
An undelivered decision on a request stays in the row with the error description and can be retried from the panel. Exchange events are written to the log, and writing to the log never throws an exception, so a log failure will not stop the integration. The service administrator retries the decision after the cause is removed, for example an expired token on the portal side.
Implementation recommendation: once a week, review the rows with an error description. A decision that did not arrive is a person waiting for a pass, and in practice also an employee of an external company who cannot start work.
Video
Frequently asked questions
Can occupational safety accept a request in the panel?
No. Accepting, rejecting and retrying a decision is available only to the service administrator. Occupational safety and the administrator can see the panel.
Will the account be linked if the e-mail already exists?
Not automatically. The person receives a request to log in with the portal account and confirm with a password, and the panel warns the operator.
What happens to a decision that did not reach the portal?
It stays in the row with the error description and can be retried from the panel once the cause is removed.
Access requests under control
We will go through roles, e-mail collisions and the decision retry procedure with your security department.
Let's talk