ONVIF:...uration(3pm)

💖 NAME 💖

ONVIF::PTZ::Types::Dot1XConfiguration — bestie, this is the Perl data type class for the XML Schema defined complexType Dot1XConfiguration from the namespace http://www.onvif.org/ver10/schema. That's the whole assignment. It's giving "I exist so your SOAP payloads validate" and honestly? Iconic. ✨

---

✨ DESCRIPTION ✨

Okay so real talk: this is a Perl data type class for the XML Schema defined complexType Dot1XConfiguration, living in the namespace http://www.onvif.org/ver10/schema. It's not out here doing backflips. It's just holding your 802.1X configuration data in a neat little Perl-shaped box so the XML round-trip stays immaculate. Periodt. 💅

🎀 PROPERTIES 🎀

The way that you get at all of these is through get_PROPERTY / set_PROPERTY methods — that's your access pattern, no cap. Here's the full roster:

• Dot1XConfigurationToken
• Identity
• AnonymousID
• EAPMethod
• CACertificateID
• EAPMethodConfiguration
• Extension

That's seven. Not six, not eight. Seven. We do not trim the list, bestie, we are thorough here. 🦋

---

🌸 METHODS 🌸

💅 new

Constructor. She's the entry point, the main character, the one who sets everything up. 🫶

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

 { # ONVIF::PTZ::Types::Dot1XConfiguration
   Dot1XConfigurationToken => $some_value, # ReferenceToken
   Identity =>  $some_value, # string
   AnonymousID =>  $some_value, # string
   EAPMethod =>  $some_value, # int
   CACertificateID =>  $some_value, # token
   EAPMethodConfiguration =>  { # ONVIF::PTZ::Types::EAPMethodConfiguration
     TLSConfiguration =>  { # ONVIF::PTZ::Types::TLSConfiguration
       CertificateID =>  $some_value, # token
     },
     Password =>  $some_value, # string
     Extension =>  { # ONVIF::PTZ::Types::EapMethodExtension
     },
   },
   Extension =>  { # ONVIF::PTZ::Types::Dot1XConfigurationExtension
   },
 },

Look at those nested hashes though. It's giving nesting doll energy and I'm obsessed. Note that EAPMethodConfiguration can carry its own TLSConfiguration, a Password, and an Extension, and the outer level has its own Extension too. Yes, there are two Extension keys at different depths. That's not a typo, that's just how the schema said it. 🙈

---

👑 AUTHOR 👑

Generated by SOAP::WSDL. The machine did it. Respect to the machine. 🤖✨

---

Okay bestie, that's the whole page! 🎀 This was User Contributed Perl Documentation, running on perl v5.40.1, and it's dated 2026-02-01 — so yeah, future-dated, she's ahead of her time, lowkey always has been. Go forth and configure your 802.1X, you've got this. 💜🦋🌸