ONVIF::...bilities(3)

✨ ONVIF::Media::Types::SecurityCapabilities ✨

Hey bestie, welcome to the ONVIF::Media::Types::SecurityCapabilities page from the ONVIF Perl docs 💖 (that's the ONVIF::...bilities(3) header, cutely folded in so you're not staring at a truncated title).

---

🌸 NAME 🌸

ONVIF::Media::Types::SecurityCapabilities — okay so this is a Perl data type class, no cap. It's the Perl data type class for the XML Schema defined complexType SecurityCapabilities from the namespace http://www.onvif.org/ver10/schema. That's it, that's the whole vibe 🫶

---

💅 DESCRIPTION 💅

Perl data type class for the XML Schema defined complexType SecurityCapabilities from the namespace http://www.onvif.org/ver10/schema. Literally exactly what it says on the tin ✨

🎀 PROPERTIES 🎀

The following properties may be accessed using get_PROPERTY / set_PROPERTY methods. So if you wanna peek or poke, that's the whole deal:

• TLS1__1 — bestie, listen 😭 this one's name got 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, 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, and XML output uses the original name: TLS1.2
• OnboardKeyGeneration — iconic, no notes 💅
• AccessPolicyConfig — also here, living its best life
• X__509Token — yup, another altered one 🙈 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 — present and accounted for ✨
• KerberosToken — slay
• RELToken — also slay
• Extension — the little nesting doll of the group 🪆

---

🔥 METHODS 🔥

🌈 new

Constructor, aka the main character method 👑. 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 — Extension inside Extension inside everything else, it's giving russian dolls and honestly? Obsessed 🦋 Pop that whole hash into new() and you're golden 💖

Heads up bestie: keep those TLS1__1, TLS1__2 and X__509Token names exactly as written in your perl code — the double underscores are on purpose, the XML just gets the dotted originals ✨

---

🧚 AUTHOR 🧚

Generated by SOAP::WSDL — not by a human, it's machine-made magic, and honestly it ate 💀✨

---

k bye bestie, go forth and get_PROPERTY responsibly 🫶

This lil page is from perl v5.42.3, dated 1980-01-01, and it's the ONVIF::...bilities(3) corner of the User Contributed Perl Documentation. Mwah 💋