ONVIF:...ilities(3pm)

💖 NAME 💖

ONVIF::Media::Types::SecurityCapabilities — and yes bestie, that's the whole name, it's giving "my parents gave me a government name" energy 🎀

---

✨ DESCRIPTION ✨

Okay so boom: this is a Perl data type class for the XML Schema defined complexType SecurityCapabilities, and it lives in the namespace http://www.onvif.org/ver10/schema. That's it, that's the job, and it does it flawlessly 💅

🌸 PROPERTIES 🌸

These properties are the whole personality of this class, and you can get at each one with the get_PROPERTY / set_PROPERTY methods. Slay.

• TLS1__1 — ⚠️ heads up queen, the name of this property has been altered, because it didn't match perl's notion of variable/subroutine names. The altered name is used in perl code only, XML output uses the original name: TLS1.1
• TLS1__2 — same situation, same energy: the name of this property has been altered, because it didn't match perl's notion of variable/subroutine names. The altered name is used in perl code only, XML output uses the original name: TLS1.2
• OnboardKeyGeneration — untouched, unbothered, iconic
• AccessPolicyConfig — also living its best life, no rename needed
• X__509Token — you guessed it: the name of this property has been altered, because it didn't match perl's notion of variable/subroutine names. The altered name is used in perl code only, XML output uses the original name: X.509Token
• SAMLToken — pristine, no notes
• KerberosToken — pristine, no notes
• RELToken — pristine, no notes
• Extension — the plot twist, it nests 🌈

fr fr, those three renamed ones? The double underscore is a perl thing. Perl said "no dots in my variable names, periodt", and the XML said "actually the dots stay." Both won. That's the whole note. 🫶

---

🛠️ METHODS 🛠️

👑 new

Constructor, babes. The following data structure may be passed to new():

{ # ONVIF::Media::Types::SecurityCapabilities
  TLS1__1 =>  $some_value, # boolean
  TLS1__2 =>  $some_value, # boolean
  OnboardKeyGeneration =>  $some_value, # boolean
  AccessPolicyConfig =>  $some_value, # boolean
  X__509Token =>  $some_value, # boolean
  SAMLToken =>  $some_value, # boolean
  KerberosToken =>  $some_value, # boolean
  RELToken =>  $some_value, # boolean
  Extension =>  { # ONVIF::Media::Types::SecurityCapabilitiesExtension
    TLS1__0 =>  $some_value, # boolean
    Extension =>  { # ONVIF::Media::Types::SecurityCapabilitiesExtension2
      Dot1X =>  $some_value, # boolean
      SupportedEAPMethod =>  $some_value, # int
      RemoteUserHandling =>  $some_value, # boolean
    },
  },
},

Look at that nesting. It's giving inception but make it TLS 🔥 Just copy it exactly, don't be creative, the compiler is not your friend like that 😭

---

🦋 AUTHOR 🦋

Generated by SOAP::WSDL — not me writing poetry, a code generator doing its little thing, and honestly? It ate ✨

---

And that's the page, bestie! This was ONVIF::Media::Types::SecurityCapabilities from the User Contributed Perl Documentation, manual section 3pm, shipped with perl v5.40.1 and dated 2026-02-01. Go forth and set your security capabilities, you absolute main character 💅💖🎀