InnerWeb
Skip to main content

FAQ: portal account login, MFA and locked accounts

The IT department hears from management about a single login for contractors and asks one question: is this a back door around our own safeguards? The answer is no, because logging in with a portal account follows the same path as logging in with a password. Below we describe what the plant checks, what the employee sees at the first sign-in and how locked accounts behave.

180 s
validity of a pending account link
Source: internal card
3
link safeguards: address match, time limit, CSRF
Source: internal card

Does logging in with a portal account bypass two-factor authentication?

It does not. Logging in through the portal follows the plant's standard path, not a separate, simplified gate. If two-factor authentication is enabled in the installation, the contractor's employee passes it exactly like any other user. The portal provides proof of identity, and the plant's rules decide on admission to the system.

This matters for the auditor: two ways of logging in do not mean two security levels. Password rules, locks and the second factor are shared, so it is enough to describe them once in the policy.

What about accounts that are locked, disabled, deleted or expired?

Accounts that are locked, disabled, deleted or expired are rejected in the same way as with a password login. Locking a contractor's account at the plant, for example after the contract ends or after an incident, also effectively closes the path through the portal. There is no need to remember a second place where access would have to be revoked.

For OHS and security this is a strong argument in talks with external companies: revoking an employee's access works in one place and covers all login paths.

Checks at portal account login: number of conditions

Checks at portal account login: number of conditionsHorizontal bar chart: four token checks, three link safeguards, four rejected account states01234conditionsToken verification (issuer,audience, time, nonce)Token verification (issuer, audience, time, nonce): 4 conditions4Account link (address, 180 s,CSRF)Account link (address, 180 s, CSRF): 3 conditions3Rejected account states(locked, disabled, deleted,expired)Rejected account states (locked, disabled, deleted, expired): 4 conditions4
Source: Summary from the feature description, internal card

What does the employee see at the first sign-in?

The first sign-in with a portal account does not end with a login to the plant. The employee is directed to the regular password login, because the password is proof that the plant account really belongs to this person. Only after this step is the portal account linked to the account at the plant.

Three safeguards apply to the link. The address from the portal must match the address of the account confirmed by password. A pending link expires after 180 seconds. The save requires confirmation with a CSRF token, after a screen showing which portal account is being attached. Each subsequent sign-in takes place without linking again.

Why doesn't the system create the account automatically?

Logging in with a portal account does not create accounts at the plant and does not match them by e-mail address. The account is bound to the person's identifier from the portal. E-mail addresses are sometimes shared or mistyped, while the identifier is stable and unambiguous. In this way nobody can take over someone else's account just by knowing their address.

How does the plant verify the identity token from the portal?

The identity token is verified with an RS256 signature, using a key fetched only from the issuer's public key set. The system checks the issuer, the audience, the validity period and a one-time nonce value. The nonce prevents reuse of an intercepted token, and the audience check means that a token issued for another service will not work with us.

The key is not entered in the configuration and is not supplied by the user. It comes from the public key set, so rotation on the issuer's side requires no intervention from the plant administrator.

Does logging in with a portal account admit someone to the site?

No. Admission to the site remains the plant's decision. Logging in confirms identity and opens the person's portal access in the installation, but the pass, permits and admission to work have their own rules. The operator reviews access requests and can reject them.

It is worth telling contractors plainly at the communication stage: a portal account shortens the formalities, but it does not guarantee entry.

Video

Frequently asked questions

Does the contractor have to remember two passwords?

The plant password is needed once, when accounts are linked, as proof of ownership. Later sign-ins are done with the portal account.

What if the e-mail address in the portal differs from the address of the account at the plant?

Linking will fail, because the address from the portal must match the address of the account confirmed by password. The contractor corrects the address in the portal, or the plant corrects it in the account.

What happens if the employee does not confirm the link within 3 minutes?

The pending link expires after 180 seconds. The employee starts the process again, with no side effects on the account.

Does the administrator have to manage the keys for token verification by hand?

No. The public key is fetched from the issuer's key set, and the plant administrator handles the machine token for the work history, not the login keys.

Sources

Let's check contractor login with your IT department

In the demo we will show the first sign-in, linking the account and the rejection of a locked account, and your team can assess the path against your access policy.

Let's talk