UniStream PLCs support multiple Redfish management services that enable secure device administration, software updates, authentication, certificate management, monitoring, and remote management through standard Redfish APIs.
The following services are available:
Account Service - User account management, role-based access control, password policy, and account lockout
Session Service - Token-based authentication using Redfish sessions
Manager Resource - Device management, network configuration, logs, and reboot operations
Certificate Management - HTTPS certificate configuration, viewing, CSR generation, and certificate replacement
Update and Task Services - Firmware and application update management, and monitoring of asynchronous update operations
For complete Redfish specification details, refer to the DMTF Redfish Specification:
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2025.3.pdf
The Account Service provides user account management and role-based access control for Redfish server.
Administrators can create, modify, and delete user accounts while enforcing password policies and account lockout behavior.
The following roles are available:
Administrator - Full access to all Redfish resources and services. Can manage accounts, configure resources, and modify own settings
Operator - Can configure resources and modify own settings. Cannot manage other accounts.
ReadOnly - Read-only access to resources. Can modify only own password and name.
Account Service Properties
Via the Set Service Property Ladder element, you can configure the service settings below. All fields have defaults and are optional to configure.
|
Property |
Default |
Description |
|
Service Enabled |
Enabled |
Enables or disables the Account Service |
|
Account Lockout Counter Reset After |
600 seconds |
Failed-attempt counter reset period |
|
Account Lockout Counter Reset Enabled |
Enabled |
Enables automatic counter reset |
|
Account Lockout Duration |
900 seconds |
Lockout duration |
|
Account Lockout Threshold |
3 |
Failed login attempts before lockout |
|
Auth Failure Logging Threshold |
3 |
Failed attempts before event logging |
|
Max Password Length |
64 |
The number of event retry attempts |
|
Min Password Length |
6 |
The interval between retries in seconds |
Account Lockout Behavior
When a user exceeds the AccountLockoutThreshold, their account is locked automatically. While locked, login attempts fail even with the correct password.
Administrators can unlock the account manually
Accounts may automatically unlock after the configured lockout duration
If AccountLockoutCounterResetEnabled is set, the failed-attempt counter resets after AccountLockoutCounterResetAfter seconds of inactivity - preventing lockout from spread-out failed attempts
Set AccountLockoutThreshold to 0 to disable lockout entirely
The Session Service provides token-based authentication for the Redfish server. You can authenticate once and reuse a session token for subsequent requests instead of sending credentials with every call.
Two authentication methods are supported and can be used interchangeably:
Basic Auth - Username and password sent with every request.
Session Auth (X-Auth-Token) - Log in once, receive a token, and use that token for subsequent requests.
Session auth is the preferred method for clients that make multiple requests, since it avoids sending credentials repeatedly over the network.
How it works
Send a request to the Sessions endpoint with a username and password
The server validates the credentials and returns a unique token in the response header
Include this token on all future requests instead of the username and password
Sessions expire automatically after an idle timeout, which resets on each use
Multiple sessions can exist simultaneously for the same user, each with its own independent token and timeout
Administrators can manage Session Service settings and delete any session. Non-administrator users can delete only their own sessions
Session Service Properties
Via the Set Service Property Ladder element, you can configure the service settings below. All fields have defaults and are optional to configure.
|
Property |
Default |
Description |
|
Service Enabled |
Enabled |
Enables or disables the Session Service |
|
Session Timeout |
1800 seconds |
Seconds of inactivity before a session is automatically closed |
|
Max Sessions |
10 |
Maximum number of concurrent sessions allowed |
|
Current Session Count |
0 |
Current number of active sessions (read-only) |