ONVIF:...ateKey(3pm)

💖 ONVIF::Analytics::Types::CertificateWithPrivateKey 💖

okay bestie, pull up a chair, because we're looking at ONVIF:...ateKey(3pm) — that's the page title, and yes, it lives in the User Contributed Perl Documentation section of the manual. It's giving very niche, very specific, very we know what we're doing energy, and honestly? We do. 🫶

---

✨ NAME ✨

ONVIF::Analytics::Types::CertificateWithPrivateKey — say that three times fast, I dare you. It's a whole mouthful but it's literally just the name of this Perl class, no cap. 🎀

---

🌸 DESCRIPTION 🌸

So here's the tea: this is a Perl data type class for the XML Schema defined complexType CertificateWithPrivateKey, and it comes from the namespace http://www.onvif.org/ver10/schema. That's it, that's the whole vibe. It's a little container that knows how to be a certificate with a private key attached, per the schema. Iconic behavior honestly. ✨

🦋 PROPERTIES 🦋

The following properties may be accessed using get_PROPERTY / set_PROPERTY methods:

• CertificateID 💅
• Certificate 🎀
• PrivateKey 🔐

Three properties. Clean. Minimal. She understood the assignment. ✨

---

💜 METHODS 💜

🌈 new 🌈

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

 { # ONVIF::Analytics::Types::CertificateWithPrivateKey
   CertificateID =>  $some_value, # token
   Certificate =>  { # ONVIF::Analytics::Types::BinaryData
     Data =>  $some_value, # base64Binary
   },
   PrivateKey =>  { # ONVIF::Analytics::Types::BinaryData
     Data =>  $some_value, # base64Binary
   },
 },

okay so let's walk through this because it's lowkey the cutest little nested hash situation you've ever seen:

• CertificateID takes $some_value, and the comment tells us that value is a token. Slay. 🎀
• Certificate takes a nested hash that's an ONVIF::Analytics::Types::BinaryData, and inside that, Data takes $some_value, which is base64Binary. Nested. Layers. Depth. We love a complexType with range. 💅
• PrivateKey is literally the same deal — another ONVIF::Analytics::Types::BinaryData, another Data => $some_value, another base64Binary. Twin behavior, fr fr. 👑

heads up bestie: those comments in the code (# token, # base64Binary) are the type annotations, not optional gossip. They're telling you what flavor of value goes there. Don't skip them. 🙈

---

👑 AUTHOR 👑

Generated by SOAP::WSDL. That's the whole author line. The machine wrote it, the machine owns it, and honestly? It ate. 💅

---

and that's the page, bestie — a tiny little certificate-and-key wrapper from the ONVIF analytics types, doing exactly what it says on the tin. 🦋

cute sign-off: this lovely lil' doc came from perl v5.40.1, dated 2026-02-01, and it answers to the name ONVIF:...ateKey(3pm). mwah. 💖✨🎀