Update Sessions Config

POST/web/v1/system/security/sessions/config JWT

Updates the authenticated user's session configuration. Supports partial updates (patch semantics) — null fields are treated as no-op.

Required Headers

Header	Example Value	Description
Content-Type	application/json	Request content type
Accept	application/json	Expected response type
X-Client-Hash		Client device fingerprint
Accept-Language	en, zh, zh-Hant, ja, vi	Response language (default: en)
Authorization	Bearer	JWT access token
X-SC-Session-Id		Secure channel session ID

Request Parameters

Name	Type	Required	In	Description
request	SessionConfigUpdateRequest	Required	body	Raw request body (encrypted via SecureChannel, auto-decrypted by the server)
ssoEnabled	Boolean	Optional	body	Enable or disable single sign-on enforcement
maxSessions	Integer	Optional	body	Maximum number of concurrent sessions (1-5)

Request Example

{
  "ssoEnabled": true,
  "maxSessions": 3
}

Success Response

Success 200

{
  "version": "1.3.0",
  "timestamp": 1709337600000,
  "success": true,
  "code": "2000",
  "message": "SUCCESS",
  "data": {
    "accountBizId": "ACC_SYS_001",
    "ssoEnabled": true,
    "maxSessions": 3,
    "passwordChangedAt": "2026-03-20T08:15:00Z",
    "lastLoginAt": "2026-03-23T12:00:00Z",
    "lastLoginIp": "192.168.***"
  }
}

The response returns the full updated SessionConfigResponse — see Get Sessions Config for field descriptions.

Error Responses

Unauthorized 401

{
  "success": false,
  "code": "4010",
  "message": "Invalid or expired token"
}

Notes

• Only ssoEnabled and maxSessions are configurable — other fields in the response are read-only.
• maxSessions must be between 1 and 5 (inclusive).
• Null fields are ignored (patch semantics), so you can update only one field at a time.