Self-Issued OpenID Provider vs OpenID Provider
<p>To make it short:</p>

<p>How exactly does an "Self-Issued OpenID Provider" differentiate from a “normal OpenID Provider” (lets say google) ?</p>

<p>I read the specification which just says :</p>

<blockquote>
  <p>"OpenID Connect supports Self-Issued OpenID Providers - personal, self-hosted OPs that issue self-signed ID Tokens. Self-Issued OPs use the special Issuer Identifier <a href="https://self-issued.me" rel="noreferrer">https://self-issued.me</a>.“</p>
</blockquote>

<p>So I understand that an „Self-Issued OpenID Provider” can be hosted by myself, and signs the the ID Tokens.</p>

<p>Is the difference that the Tokens from the “normal OpenID Provider” are signed with an certificate which is trusted (e.g. because it's signed by a root CA certificate which is already in the certificate store), and can be validated without the need of sending the public-key within the response ?</p>

<p>Eventually somebody can clarify this, I would appreciate it much.</p>

<p>Thanks in advance and best regards ! </p>