5.4.4. Info keyset

A keyset info command is used to view details of a keyset.

The keyset info command is an info element in the keyset namespace (http://www.nic.cz/xml/epp/keyset-1.3).

The command must be contained in the <info> command type.

5.4.4.1. Command element structure

The <keyset:info> element must declare the keyset namespace and schema and it must contain the following child element:

Example
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
   <command>
      <info>
         <keyset:info xmlns:keyset="http://www.nic.cz/xml/epp/keyset-1.3"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/keyset-1.3 keyset-1.3.2.xsd">
            <keyset:id>KID-MYKEYSET</keyset:id>
         </keyset:info>
      </info>
      <clTRID>gyyp005#17-07-31at13:03:07</clTRID>
   </command>
</epp>
FRED-client equivalent
> info_keyset NID-MYNSSET

5.4.4.2. Response element structure

The response from the FRED EPP server contains the result, response data, and transaction identification.

See also Success or failure of a command.

The response data element (<resData>) contains a single child element <keyset:infData> which declares the keyset namespace and schema and it contains the following child elements:

Example
<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
   <response>
      <result code="1000">
         <msg>Command completed successfully</msg>
      </result>
      <resData>
         <keyset:infData xmlns:keyset="http://www.nic.cz/xml/epp/keyset-1.3"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/keyset-1.3 keyset-1.3.2.xsd">
            <keyset:id>KID-MYKEYSET</keyset:id>
            <keyset:roid>K0009907596-CZ</keyset:roid>
            <keyset:status s="linked">Has relation to other records in the registry</keyset:status>
            <keyset:clID>REG-MYREG</keyset:clID>
            <keyset:crID>REG-MYREG</keyset:crID>
            <keyset:crDate>2017-07-11T13:28:45+02:00</keyset:crDate>
            <keyset:upID>REG-MYREG</keyset:upID>
            <keyset:upDate>2017-07-20T20:04:35+02:00</keyset:upDate>
            <keyset:authInfo>aBcD234</keyset:authInfo>
            <keyset:dnskey>
               <keyset:flags>257</keyset:flags>
               <keyset:protocol>3</keyset:protocol>
               <keyset:alg>5</keyset:alg>
               <keyset:pubKey>aXN4Y2lpd2ZicWtkZHF4dnJyaHVtc3BreXN6ZGZy</keyset:pubKey>
            </keyset:dnskey>
            <keyset:dnskey>
               <keyset:flags>257</keyset:flags>
               <keyset:protocol>3</keyset:protocol>
               <keyset:alg>5</keyset:alg>
               <keyset:pubKey>eGVmbmZrY3lvcXFwamJ6aGt2YXhteXdkc2tjeXBp</keyset:pubKey>
            </keyset:dnskey>
            <keyset:tech>CID-TECH2</keyset:tech>
         </keyset:infData>
      </resData>
      <trID>
         <clTRID>gyyp005#17-07-31at13:03:07</clTRID>
         <svTRID>ReqID-0000141004</svTRID>
      </trID>
   </response>
</epp>