Deployed cd20d918 to develop in public with MkDocs 1.6.0 and mike 2.1.1

      <link rel="icon" href="/develop/images/favicon.png">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.26">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.27">

      <link rel="icon" href="../images/favicon.png">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.26">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.27">

      <link rel="icon" href="../images/favicon.png">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.26">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.27">

        <label class="md-nav__link md-nav__link--active" for="__toc">

  <span class="md-ellipsis">

    Architecture

  </span>

          <span class="md-nav__icon md-icon"></span>

        </label>

      <a href="./" class="md-nav__link md-nav__link--active">

      </a>

<nav class="md-nav md-nav--secondary" aria-label="Table of contents">

    <label class="md-nav__title" for="__toc">

      <span class="md-nav__icon md-icon"></span>

      Table of contents

    </label>

    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>

        <li class="md-nav__item">

  <a href="#register-ns" class="md-nav__link">

    <span class="md-ellipsis">

      Register NS

    </span>

  </a>

</li>

        <li class="md-nav__item">

  <a href="#vault-ns" class="md-nav__link">

    <span class="md-ellipsis">

      Vault NS

    </span>

  </a>

</li>

        <li class="md-nav__item">

  <a href="#mon-ns" class="md-nav__link">

    <span class="md-ellipsis">

      Mon NS

    </span>

  </a>

</li>

        <li class="md-nav__item">

  <a href="#new-architecture" class="md-nav__link">

    <span class="md-ellipsis">

      New Architecture

    </span>

  </a>

</li>

    </ul>

</nav>

    </li>

    <label class="md-nav__title" for="__toc">

      <span class="md-nav__icon md-icon"></span>

      Table of contents

    </label>

    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>

        <li class="md-nav__item">

  <a href="#register-ns" class="md-nav__link">

    <span class="md-ellipsis">

      Register NS

    </span>

  </a>

</li>

        <li class="md-nav__item">

  <a href="#vault-ns" class="md-nav__link">

    <span class="md-ellipsis">

      Vault NS

    </span>

  </a>

</li>

        <li class="md-nav__item">

  <a href="#mon-ns" class="md-nav__link">

    <span class="md-ellipsis">

      Mon NS

    </span>

  </a>

</li>

        <li class="md-nav__item">

  <a href="#new-architecture" class="md-nav__link">

    <span class="md-ellipsis">

      New Architecture

    </span>

  </a>

</li>

    </ul>

</nav>

                  </div>

                </div>

<p><img src="../images/logos/OpenCAPIF.png" alt="drawing" width="200"/></p>

<h1 id="architecture">Architecture</h1>

<h1 id="architecture"><strong>Architecture</strong></h1>

<p>The CAPIF architecture has three main components, Register Service, Vault and CCF, which are represented in the following image:</p>

<p><img alt="New Architecture" src="../images/architecture/New_Architecture.png" /></p>

<p>Each component is separated into different namespaces and all communications between them use Rest APIs.</p>

<p>Apart from the communication between components, there are 2 other entities that can use them:</p>

<ul>

<li><strong>Admin/superadmin</strong>: Responsible for managing users with the Register or carrying out special operations in the CCF.</li>

<li><strong>Users</strong>: They are those who want to use CAPIF, registering as a user in the Register and as Invoker or Provider in the CCF.</li>

</ul>

<h2 id="register-ns"><strong>Register NS</strong></h2>

<p>This namespace belongs to the Register service, and we find 2 components:</p>

<ul>

<li><strong>Register Service</strong>: It is responsible for managing all users who use CAPIF, in addition to providing the necessary information for its use.</li>

<li><strong>Register MONGO DATABASE</strong>: It is the Register database, in it we store all the information about registered users.</li>

</ul>

<h2 id="vault-ns"><strong>Vault NS</strong></h2>

<p>This namespace belongs to Vault. </p>

<p>This component is responsible for managing all CAPIF certificates, so other components such as the Register or the CCF communicate with it to create new certificates or request keys.</p>

<h2 id="mon-ns"><strong>Mon NS</strong></h2>

<p>This is the main namespace of CAPIF, since it contains all the CCF services in addition to other components:</p>

<ul>

<li><strong>NGINX</strong>: Responsible for acting as a reverse proxy to distribute CAPIF requests to the different services, controlling whether or not they are authorized to access them.</li>

<li><strong>REDIS</strong>: Used for internal communication of services.</li>

<li><strong>CAPIF MONGO DATABASE</strong>: CAPIF database, where all information related to CAPIF services such as invokers, registered providers or published services is stored.</li>

<li><strong>HELPER</strong>: Service that simplifies integration with third parties such as external management portals.</li>

</ul>

<h2 id="new-architecture"><strong>New Architecture</strong></h2>

<p>You can check the details of all these changes in the conversation on the <a href="https://labs.etsi.org/rep/ocf/community/-/wikis/New%20architecture">OCF wiki</a>.</p>

      <link rel="icon" href="../../images/favicon.png">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.26">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.27">

      <link rel="icon" href="../../images/favicon.png">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.26">

      <meta name="generator" content="mkdocs-1.6.0, mkdocs-material-9.5.27">