<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>License on inetshell</title><link>https://inet.sh/en/tags/license/</link><description>Recent content in License on inetshell</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 19 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://inet.sh/en/tags/license/index.xml" rel="self" type="application/rss+xml"/><item><title>Read an HP iLO license key without the web UI</title><link>https://inet.sh/en/posts/ilo/get-license-key/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://inet.sh/en/posts/ilo/get-license-key/</guid><description>Extract an HP iLO license key from the xmldata?item=CpqKey XML endpoint, with no web-console login.</description><content:encoded><![CDATA[<h2 id="tldr">TL;DR</h2>
<p><code>curl -sk &quot;https://&lt;ilo-ip&gt;/xmldata?item=CpqKey&quot;</code> — license key is in the XML, no UI login.</p>
<p>iLO Advanced is licensed by key. If you inherited a ProLiant and the UI will not open (cert, Java, firmware), the BMC still publishes an inventory XML.</p>
<h2 id="the-endpoint">The endpoint</h2>
<div class="highlight"><div class="chroma">
<table class="lntable"><tr><td class="lntd">
<pre tabindex="0" class="chroma"><code><span class="lnt">1
</span></code></pre></td>
<td class="lntd">
<pre tabindex="0" class="chroma"><code class="language-shell" data-lang="shell"><span class="line"><span class="cl">curl -sk <span class="s2">&#34;https://&lt;ilo-ip&gt;/xmldata?item=CpqKey&#34;</span>
</span></span></code></pre></td></tr></table>
</div>
</div><p>In a browser: <code>https://&lt;ilo-ip&gt;/xmldata?item=CpqKey</code>.</p>
<p>The body is XML with the product and the key (or an unlicensed state). This is not Redfish; it is iLO&rsquo;s <code>xmldata</code> interface, the one old HP SIM scripts used.</p>
<h2 id="notes">Notes</h2>
<ul>
<li><code>-k</code> because the iLO certificate is almost never from a public CA.</li>
<li>Some iLOs still serve this over <strong>HTTP</strong> (<code>http://&lt;ilo-ip&gt;/xmldata?item=CpqKey</code>) if HTTPS will not negotiate.</li>
<li>Treat the key as a secret. Do not commit it or paste it.</li>
<li>Reading it does not activate anything: it only <strong>reads</strong> what is already stored on the BMC. Applying a different key is still <code>license</code> in CLP or the UI.</li>
</ul>
<p>See also: <a href="/en/posts/ilo/cli-commands/">iLO CLI commands</a>.</p>
]]></content:encoded></item></channel></rss>