Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Operator → Add Common Sim Security

AI-generated

Overview

This node integrates with the Summa API to add common SIM security settings for a specified operator. It is useful in telecom or mobile network management scenarios where operators need to configure or update SIM security parameters programmatically. For example, a user can automate the process of adding encryption keys, authentication schemes, and other security-related parameters to an operator's profile within their system.

Properties

Name Meaning
Operator Name The name of the operator for which the common SIM security settings will be added.
Send Json A boolean flag indicating whether to send the data as raw JSON or use individual fields.
Json Data The raw JSON data containing all necessary SIM security parameters (used if Send Json is true).
Additional Fields A collection of optional fields specifying individual SIM security parameters when not sending raw JSON. These include: Name, Op, Transport Key, Amf, Encryption, Authentication Scheme, Active (boolean), Algorithm, R1-R6 (numbers), C1-C5 (strings), K_length, Ck_length, Ik_length, Res_length, Maca_length, Macs_length, Keccak Iterations (number), Top.

Output

The node outputs JSON data representing the result of the Add Common SIM Security operation. This typically includes confirmation of the operation success, details of the updated security settings, or error information if the operation failed. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Summa API.
  • Uses the HttpClient class from the bundled backend code to make HTTP requests.
  • Relies on internal state and operation resolver classes to handle resource-operation logic.
  • The node expects the Summa API endpoint and version configured via credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing operator name may cause the API call to fail.
    • Incorrectly formatted JSON data when "Send Json" is enabled can lead to parsing errors.
    • Missing required fields in additional fields collection might cause incomplete or rejected requests.
    • Network or authentication failures due to invalid API credentials.
  • Error messages:

    • Errors related to authentication usually indicate invalid or expired API keys; recheck and update credentials.
    • Validation errors from the API often specify which field is missing or malformed; verify input properties accordingly.
    • Timeout or connection errors suggest network issues or incorrect API endpoint configuration.

Links and References


Note: The above summary is based solely on static analysis of the provided source code and property definitions.

Discussion