ONVIF:...Request(3pm)

✨ NAME ✨

ONVIF::Device::Elements::GetPkcs10Request — bestie, you've landed in the ONVIF:...Request(3pm) part of the perl manual, and this is the whole vibe 💖

---

🌸 DESCRIPTION 🌸

Okay so, real talk: this is a Perl data type class for the XML Schema defined element GetPkcs10Request 🎀

Where does it live? Namespace: http://www.onvif.org/ver10/device/wsdl — that's the ONVIF device WSDL, iykyk 🫶

That's it. That's the class. It's giving "small but mighty" ✨

---

🦋 PROPERTIES 🦋

These are the properties you can touch, and you get at them with the get_PROPERTY / set_PROPERTY methods 🧚

• CertificateID — grab it or set it like this:

$element->set_CertificateID($data);
$element->get_CertificateID();

(its type is token, no cap 💅)

• Subject — same deal, two little calls:

$element->set_Subject($data);
$element->get_Subject();

(its type is string 🌸)

• Attributes — again with the pair:

$element->set_Attributes($data);
$element->get_Attributes();

(this one's a ONVIF::Device::Types::BinaryData, lowkey fancy 👑)

---

💅 METHODS 💅

new

my $element = ONVIF::Device::Elements::GetPkcs10Request->new($data);

Constructor, babes 🎀 Here's the data structure you may pass to new() — copy it exactly, don't freestyle:

{
  CertificateID =>  $some_value, # token
  Subject =>  $some_value, # string
  Attributes =>  { # ONVIF::Device::Types::BinaryData
    Data =>  $some_value, # base64Binary
  },
},

Look at Attributes nested in there with its own Data key — yes, base64Binary, no cap. Don't flatten it, bestie 🙈

---

⭐ AUTHOR ⭐

Generated by SOAP::WSDL — not a human, a machine, and honestly? It ate 🔥

---

And that's the whole page, main character energy from top to bottom 💖 This was perl v5.40.1, dated 2026-02-01, in the ONVIF:...Request(3pm) section — go forth and construct your elements, bestie 🌈🦋✨