Actions182
- LTE Subscription Actions
- Get Access Restriction Data For LTE
- Get Apn Info
- Get Lte Profile
- Set Lte Tele Service
- Get Lte Regional Subscription
- Get Scef Permissions
- Set APN Assignations To LTE Subscription
- Get EDRX Cycle Lengths
- Add Apn
- Get V2X Subscription Data
- Set Scef Permissions
- Set EDRX Cycle Lengths
- Set Access Restriction Data For LTE
- Set APNs To LTE Subscription
- Set APN Address Assignations To LTE Subscription
- Add LTE Subscription
- Set SCS Permissions
- Get SCS Permissions
- Get LTE ODB
- Add Custom LTE ODB
- Set LTE ODB Profile
- Get APN Assignations From LTE Subscription
- Remove APN Address Assignation From LTE Subscription
- Sim Swap Actions
- WLAN Subscription Actions
- HLR Subscription Actions
- Set HLR Profile
- Set PDP Address Assignation
- Set HLR Regional Subscription
- Remove PDP
- Remove GMLC Number
- Get HLR Teleservice
- Set MSRN Profile
- Remove PDP Assignations
- Set GMLC Numbers
- Get USSD Profile
- Set Camel Configuration
- Add Custom HLR ODB
- Add Camel Service
- Add GMLC Number
- Get GMLC Numbers
- Remove Camel Service
- Remove HLR Regional Subscription
- Set CSE Notification Profile
- Remove MSRN Profile
- Get ODB
- get HLR Profile
- Add PDP
- Get Camel Info
- Set HLR Teleservice
- Set SS Options
- Sim Swap Direct Without Remove
- Get Camel Configuration
- Clear All GMLC Number
- Set PDPs
- Apply Custom HLR ODB Settings
- Get Bearer Service
- Get Access Restriction Data Profile
- Get HLR Regional Subscription
- Remove PDP Address Assignation
- Add USSD Profile
- Set PDP Assignations
- Remove USSD Profile
- Set Access Restriction Data Profile
- Apply Subscription Settings
- Get PDP Info
- Get PDP Assignations
- Set HLR ODB Profile
- Remove CSE Notification Profile
- Get CSE Notification Profile
- Get HLR ODB
- Get MSRN Profile
- SS Subscription Actions
- Add Supplementary Service By Msisdn
- Add Call Forwarding Custom Supplementary Service
- Get All Supplementary Services By MSISDN
- Remove All Supplementary Service
- Remove All Supplementary Service By MSISDN
- Get Call Forward Information
- Get All Supplementary Services
- Remove Supplementary Service
- Add Supplementary Service
- Add Call Forwarding Custom Supplementary Service By MSISDN
- Get Call Forward Information By MSISDN
- Remove Supplementary Service By MSISDN
- SS Subscription SOAP Actions
- Get Imsi By Imsi
- Get Msisdn By Msisdn
- Create Basic Supplementary Service For SS Subscription
- Create Call Forward Supplementary Service For SS Subscription
- Create Calling Name Presentation For SS Subscription
- Create Call Line Identification Presentation For SS Subscription
- Create Call Line Identification Restriction For SS Subscription
- MSISDN Actions
- Subscriber Actions
- IMS Subscription Actions
- Send Cancel Location To Current VLR Of IMSI
- Add Transparent Data To IMPU
- Remove Transparent Data From IMPU
- Get IMS Volatile Data
- Add Service Profile To IMPU
- Add Public User Identity
- Add Private User Identity
- Remove Service Profile From IMPU
- Set GBA User Sec Settings Template To IMS Subscription
- Remove Public User Identity
- Get GBA User Sec Settings Template
- Get GBA User Sec Settings
- Delete IMS Subscription For IMSI
- IMSI Actions
- CRUD Operator Actions
- Operator Actions
- Sim Actions
- Send Protocol Actions
- Send Cancel Location MME
- Send RTR For IMPI
- Send Cancel Location To Current SGSN Of Imsi
- Send Cancel Location To Current VLR Of IMSI
- Send Cancel Location VLR
- Send Cancel Location SGSN
- Send Diameter Cancel Location SGSN
- Send Cancel Location To Current SGSN
- Send Cancel Location To All Currents Of IMSI
- Send Cancel Location To Current MME Of IMSI
- Send RTR For IMPU
- Send Cancel Location To Current VLR
- Send Cancel Location To Current MME
- CRUD PLMN Actions
- Templates Actions
Overview
The "Edit Common Sim Security" operation within the "Operator" resource allows users to modify security settings related to a common SIM profile for an operator. This node is useful in telecom or mobile network management scenarios where operators need to update or configure SIM security parameters programmatically via the Summa API.
Typical use cases include:
- Updating encryption and authentication schemes for SIM cards.
- Changing transport keys or algorithm parameters used in SIM security.
- Activating or deactivating specific security configurations.
- Bulk updating security settings by sending raw JSON data.
For example, a telecom operator might use this node to update the encryption algorithm and keys for all SIMs under a particular operator name, ensuring compliance with new security standards.
Properties
| Name | Meaning |
|---|---|
| Operator Name | The name of the operator whose common SIM security settings are being edited. |
| Current Common Sim Security Name | The identifier/name of the existing common SIM security configuration to be updated. |
| Send Json | Boolean flag indicating whether to send the entire security configuration as raw JSON (true) or use individual fields (false). |
| Json Data | Raw JSON data representing the full common SIM security configuration (required if Send Json is true). |
| Additional Fields | A collection of optional individual fields to specify security parameters when Send Json is false. These include: - Name - Op - Transport Key - Amf - Encryption - Authentication Scheme - Active (boolean) - Algorithm - R1 through R6 (numbers) - C1 through C5 (strings) - K_length, Ck_length, Ik_length, Res_length, Maca_length, Macs_length (strings) - Keccak Iterations (number) - Top |
Output
The node outputs JSON data reflecting the result of the edit operation on the common SIM security configuration. This typically includes confirmation of the updated settings or error details if the operation failed.
If binary data were involved (not indicated here), it would represent files or encoded security blobs, but this node focuses on JSON-based configuration data.
Dependencies
- Requires connection to the Summa API service.
- Needs an API key credential configured in n8n for authenticating requests to the Summa API.
- Uses internal helper classes for HTTP communication and state management.
- No other external dependencies are required beyond the Summa API access.
Troubleshooting
- Missing or invalid credentials: Ensure that the API key credential for the Summa API is correctly set up and tested.
- Invalid JSON format: When using the "Send Json" option, ensure the JSON data is well-formed and matches the expected schema.
- Required fields missing: Both "Operator Name" and "Current Common Sim Security Name" are mandatory; omitting them will cause errors.
- API errors: If the Summa API returns errors, verify that the operator and security names exist and that the user has permission to edit them.
- Field validation: Numeric fields like R1-R6 and Keccak Iterations should be valid numbers; strings should conform to expected formats.
Links and References
- Summa API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General information on SIM security concepts: SIM Card Security
Note: The above summary is based solely on static analysis of the provided source code and property definitions.