ONVIF::...bilities(3)

💖 ONVIF::Analytics::Types::SecurityCapabilities 💖

okay so bestie, this is the manual page ONVIF::...bilities(3) from the User Contributed Perl Documentation, and it’s literally all about the Perl class for the XML Schema complexType SecurityCapabilities. Slay.

---

✨ NAME ✨

ONVIF::Analytics::Types::SecurityCapabilities — the main-character Perl data type class for the XML Schema defined complexType SecurityCapabilities from the namespace http://www.onvif.org/ver10/schema. periodt.

---

🌸 DESCRIPTION 🌸

This is a Perl data type class for the XML Schema defined complexType SecurityCapabilities from the namespace http://www.onvif.org/ver10/schema. It’s giving very specific, very structured, very XML girlie. 🎀

🧚 PROPERTIES 🧚

These properties may be accessed using get_PROPERTY / set_PROPERTY methods. yes bestie, that’s the whole vibe:

• TLS1__1 — the TLS 1.1 property. Heads up: 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 — the TLS 1.2 property. Same situation, bestie: 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 — the OnboardKeyGeneration property. no rename drama here. 💅
• AccessPolicyConfig — the AccessPolicyConfig property. iconic, honestly.
• X__509Token — the X.509 token property. Note time: 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 — the SAMLToken property. we love a token moment. 🫶
• KerberosToken — the KerberosToken property. another token, another slay.
• RELToken — the RELToken property. token number three, no cap.
• Extension — the Extension property. it opens the door to the extension structure down in new(), iykyk. 🦋

---

👑 METHODS 👑

🍓 new

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

        { # ONVIF::Analytics::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::Analytics::Types::SecurityCapabilitiesExtension
            TLS1__0 =>  $some_value, # boolean
            Extension =>  { # ONVIF::Analytics::Types::SecurityCapabilitiesExtension2
              Dot1X =>  $some_value, # boolean
              SupportedEAPMethod =>  $some_value, # int
              RemoteUserHandling =>  $some_value, # boolean
            },
          },
        },

look at that nested extension situation. it’s giving structured data realness. 🌈

---

🎀 AUTHOR 🎀

Generated by SOAP::WSDL. that’s the author line, bestie. no notes.

---

mwah 💋 this cutie is from perl v5.42.3, dated 1980-01-01, and the manual page is ONVIF::...bilities(3) — User Contributed Perl Documentation and all. 💜