deploy: EGI-Federation/documentation@856e744

EGI-Federation · Mar 3, 2024 · 52def6d · 52def6d
1 parent 0bf4b45
commit 52def6d
Show file tree

Hide file tree

Showing 223 changed files with 515 additions and 614 deletions.
diff --git a/about/concepts/index.html b/about/concepts/index.html
diff --git a/about/contributing/git/index.html b/about/contributing/git/index.html
diff --git a/about/contributing/index.html b/about/contributing/index.html
diff --git a/about/contributing/shortcodes/index.html b/about/contributing/shortcodes/index.html
diff --git a/about/contributing/style/index.html b/about/contributing/style/index.html
diff --git a/about/index.html b/about/index.html
diff --git a/internal/accounting/index.html b/internal/accounting/index.html
diff --git a/internal/accounting/service-information/index.html b/internal/accounting/service-information/index.html
diff --git a/internal/collaboration-tools/certificates/index.html b/internal/collaboration-tools/certificates/index.html
diff --git a/internal/collaboration-tools/index.html b/internal/collaboration-tools/index.html
diff --git a/internal/collaboration-tools/mailing-lists/index.html b/internal/collaboration-tools/mailing-lists/index.html
diff --git a/internal/collaboration-tools/service-information/index.html b/internal/collaboration-tools/service-information/index.html
diff --git a/internal/collaboration-tools/sso/index.html b/internal/collaboration-tools/sso/index.html
diff --git a/internal/configuration-database/access/index.html b/internal/configuration-database/access/index.html
diff --git a/internal/configuration-database/adding-new-projects/index.html b/internal/configuration-database/adding-new-projects/index.html
diff --git a/internal/configuration-database/adding-service-endpoint/index.html b/internal/configuration-database/adding-service-endpoint/index.html
diff --git a/internal/configuration-database/api/index.html b/internal/configuration-database/api/index.html
diff --git a/internal/configuration-database/downtimes/index.html b/internal/configuration-database/downtimes/index.html
diff --git a/internal/configuration-database/extension-properties/index.html b/internal/configuration-database/extension-properties/index.html
diff --git a/internal/configuration-database/faq/index.html b/internal/configuration-database/faq/index.html
diff --git a/internal/configuration-database/index.html b/internal/configuration-database/index.html
diff --git a/internal/configuration-database/ngi-core-services/index.html b/internal/configuration-database/ngi-core-services/index.html
diff --git a/internal/configuration-database/ngis/index.html b/internal/configuration-database/ngis/index.html
diff --git a/internal/configuration-database/scopes/index.html b/internal/configuration-database/scopes/index.html
diff --git a/internal/configuration-database/service-entities/index.html b/internal/configuration-database/service-entities/index.html
diff --git a/internal/configuration-database/service-groups/index.html b/internal/configuration-database/service-groups/index.html
diff --git a/internal/configuration-database/service-information/index.html b/internal/configuration-database/service-information/index.html
diff --git a/internal/configuration-database/service-registration-requirements/index.html b/internal/configuration-database/service-registration-requirements/index.html
diff --git a/internal/configuration-database/service-types/index.html b/internal/configuration-database/service-types/index.html
diff --git a/internal/configuration-database/sites/index.html b/internal/configuration-database/sites/index.html
diff --git a/internal/configuration-database/users-roles/approve-revoke/index.html b/internal/configuration-database/users-roles/approve-revoke/index.html
diff --git a/internal/configuration-database/users-roles/index.html b/internal/configuration-database/users-roles/index.html
diff --git a/internal/configuration-database/users-roles/managing-accounts/index.html b/internal/configuration-database/users-roles/managing-accounts/index.html
diff --git a/internal/configuration-database/users-roles/managing-roles/index.html b/internal/configuration-database/users-roles/managing-roles/index.html
diff --git a/internal/getting-started/index.html b/internal/getting-started/index.html
diff --git a/internal/guidelines-software-development/index.html b/internal/guidelines-software-development/index.html
diff --git a/internal/helpdesk/account-and-privileges/index.html b/internal/helpdesk/account-and-privileges/index.html
diff --git a/internal/helpdesk/features/alarm-tickets/index.html b/internal/helpdesk/features/alarm-tickets/index.html
diff --git a/internal/helpdesk/features/index.html b/internal/helpdesk/features/index.html
diff --git a/internal/helpdesk/features/issue-type-values/index.html b/internal/helpdesk/features/issue-type-values/index.html
diff --git a/internal/helpdesk/features/quality-of-support-levels/index.html b/internal/helpdesk/features/quality-of-support-levels/index.html
diff --git a/internal/helpdesk/features/report-generator/index.html b/internal/helpdesk/features/report-generator/index.html
diff --git a/internal/helpdesk/features/team-tickets/index.html b/internal/helpdesk/features/team-tickets/index.html
diff --git a/internal/helpdesk/features/ticket-priority/index.html b/internal/helpdesk/features/ticket-priority/index.html
diff --git a/internal/helpdesk/features/ticket-scope/index.html b/internal/helpdesk/features/ticket-scope/index.html
diff --git a/internal/helpdesk/features/tickets-to-multiple-sites/index.html b/internal/helpdesk/features/tickets-to-multiple-sites/index.html
diff --git a/internal/helpdesk/index.html b/internal/helpdesk/index.html
diff --git a/internal/helpdesk/service-information/index.html b/internal/helpdesk/service-information/index.html
diff --git a/internal/helpdesk/support-staff-guide/index.html b/internal/helpdesk/support-staff-guide/index.html
diff --git a/internal/helpdesk/user-guide/index.html b/internal/helpdesk/user-guide/index.html
diff --git a/internal/helpdesk/workflows/index.html b/internal/helpdesk/workflows/index.html
diff --git a/internal/helpdesk/workflows/waiting-for-submitter/index.html b/internal/helpdesk/workflows/waiting-for-submitter/index.html
diff --git a/internal/index.html b/internal/index.html
diff --git a/internal/messaging/index.html b/internal/messaging/index.html
diff --git a/internal/messaging/service-information/index.html b/internal/messaging/service-information/index.html
diff --git a/internal/monitoring/index.html b/internal/monitoring/index.html
diff --git a/internal/monitoring/service-information/index.html b/internal/monitoring/service-information/index.html
diff --git a/internal/operations-portal/index.html b/internal/operations-portal/index.html
diff --git a/internal/operations-portal/service-information/index.html b/internal/operations-portal/service-information/index.html
diff --git a/internal/operations-portal/using-vapor/index.html b/internal/operations-portal/using-vapor/index.html
diff --git a/internal/security-coordination/index.html b/internal/security-coordination/index.html
diff --git a/internal/security-coordination/monitoring/index.html b/internal/security-coordination/monitoring/index.html
diff --git a/internal/security-coordination/monitoring/pakiti/index.html b/internal/security-coordination/monitoring/pakiti/index.html
diff --git a/internal/security-coordination/service-information/index.html b/internal/security-coordination/service-information/index.html
diff --git a/offline-search-index.60aeeafcacf21eca4db7a3fbd21fdaf8.json b/offline-search-index.60aeeafcacf21eca4db7a3fbd21fdaf8.json
diff --git a/offline-search-index.6563c22685696e3098ea07408f5504cd.json b/offline-search-index.6563c22685696e3098ea07408f5504cd.json
diff --git a/providers/check-in/idp/index.html b/providers/check-in/idp/index.html
diff --git a/providers/check-in/index.html b/providers/check-in/index.html
diff --git a/providers/check-in/index.xml b/providers/check-in/index.xml
@@ -547,8 +547,12 @@ integration with the &lt;strong>development&lt;/strong> instance of Check-in. In
 development instance service requests can be self-reviewed without the need
 to wait for approval from an administrator. As with the demo instance, the
 development instance allows for testing authentication and authorisation
-without affecting the production Check-in service. &lt;strong>NB: the list of
-supported Identity Providers in the development instance is limited.
+without affecting the production Check-in service. &lt;strong>NB: The development
+environment is intended for testing the latest features of Check-in and
+may differ from the demo and production environments in terms of stability
+and functionality.
+Keep in mind that the supported Identity Providers in the development
+instance are limited.
 Therefore, we recommend using any of the social identity providers or the
 &lt;a href="https://sso.egi.eu/admin/">EGI SSO&lt;/a> to test the login workflow when using
 the development instance.&lt;/strong>&lt;/li>
@@ -2285,114 +2289,7 @@ setup earlier:&lt;/p>
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#000">$manageTokens&lt;/span> &lt;span style="color:#ce5c00;font-weight:bold">=&lt;/span> &lt;span style="color:#000">$issuer&lt;/span> &lt;span style="color:#ce5c00;font-weight:bold">.&lt;/span> &lt;span style="color:#4e9a06">&amp;#34;manage/user/services&amp;#34;&lt;/span>&lt;span style="color:#000;font-weight:bold">;&lt;/span>
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#000">$sessionName&lt;/span> &lt;span style="color:#ce5c00;font-weight:bold">=&lt;/span> &lt;span style="color:#4e9a06">&amp;#34;simple-oidc-client-php&amp;#34;&lt;/span>&lt;span style="color:#000;font-weight:bold">;&lt;/span>
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#000">$sessionLifetime&lt;/span> &lt;span style="color:#ce5c00;font-weight:bold">=&lt;/span> &lt;span style="color:#0000cf;font-weight:bold">60&lt;/span>&lt;span style="color:#ce5c00;font-weight:bold">*&lt;/span>&lt;span style="color:#0000cf;font-weight:bold">60&lt;/span>&lt;span style="color:#000;font-weight:bold">;&lt;/span> &lt;span style="color:#8f5902;font-style:italic">// must be equal to access token validation time in seconds
-&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="client-migration-to-keycloak">Client Migration to Keycloak&lt;/h3>
-&lt;p>The migration guide below applies to OIDC clients registered in the
-&lt;strong>Development&lt;/strong>, &lt;strong>Demo&lt;/strong> and &lt;strong>Production&lt;/strong> environments of Check-in.&lt;/p>
-&lt;p>&lt;strong>Development and Demo&lt;/strong>: Beginning June 24, 2022, clients using the legacy
-Check-in OIDC endpoints will no longer be supported.&lt;/p>
-&lt;p>&lt;strong>Production&lt;/strong>: Beginning October 21, 2022, clients using the legacy Check-in
-OIDC endpoints will no longer be supported.&lt;/p>
-&lt;div class="alert alert-info" role="alert">
-&lt;h4 class="alert-heading">Note&lt;/h4>
-For OpenStack Services please read the
-OpenStack specific migration guide on
-&lt;a href="../../cloud-compute/openstack/aai.md#client-migration-to-keycloak">Cloud Compute documentation&lt;/a>.
-&lt;/div>
-&lt;h4 id="how-to-migrate-your-service-to-keycloak-1">How to Migrate your Service to Keycloak&lt;/h4>
-&lt;p>All the clients that were registered in MITREid Connect have been moved to
-Keycloak preserving all the options (Client ID, Client Secret, Redirect URIs
-etc.), so you do not need to re-register your Service.&lt;/p>
-&lt;h5 id="new-endpoints">New Endpoints&lt;/h5>
-&lt;p>The first thing you need to do is to update the OIDC endpoints according to the
-&lt;a href="#endpoints">Endpoints&lt;/a> table. If the Application/Library supports Dynamic
-Discovery, then you need to update on the &lt;code>issuer&lt;/code>. Otherwise, you need to
-update all the Endpoints separately.&lt;/p>
-&lt;h5 id="size-of-the-tokens">Size of the Tokens&lt;/h5>
-&lt;p>The size of the Access/Refresh Tokens that are issued by Keycloak is larger of
-the respective Tokens created by MITREid Connect. For example, the size of an
-Access Token is around 1400 characters, depending on the information that are
-included in the payload of the JWT. So make sure that your OIDC implementation
-can handle larger Tokens.&lt;/p>
-&lt;h5 id="logout">Logout&lt;/h5>
-&lt;p>The Redirect URI query parameter in the logout request has been changed from
-&lt;code>redirect&lt;/code> to &lt;code>post_logout_redirect_uri&lt;/code> and must be URL encoded. Also, the
-value of the &lt;code>post_logout_redirect_uri&lt;/code> must be defined in the &lt;strong>Valid Redirect
-URIs&lt;/strong> of the Service configuration in the EGI Federation Registry.&lt;/p>
-&lt;h5 id="token-introspection">Token Introspection&lt;/h5>
-&lt;p>The Token Introspection is available to all the clients that are using any
-authentication method (&lt;code>client_secret_basic&lt;/code>, &lt;code>client_secret_post&lt;/code>,
-&lt;code>client_secret_jwt&lt;/code> or &lt;code>private_key_jwt&lt;/code>) (Confidential Clients) to the Token
-Endpoint. Public Clients (clients that do not use any authentication method)
-will not be able to get a successful response from the Introspection Endpoint.
-Saying that, the &amp;ldquo;Introspection&amp;rdquo; option in the EGI Federation Registry will be
-removed.&lt;/p>
-&lt;h5 id="pkce">PKCE&lt;/h5>
-&lt;p>If you are &lt;strong>not&lt;/strong> using PKCE (Proof Key for Code Exchange), please make sure to
-&lt;strong>disable&lt;/strong> the &amp;ldquo;PKCE Code Challenge Method&amp;rdquo; in the Service configuration in
-&lt;a href="https://aai.egi.eu/federation">EGI Federation Registry&lt;/a>, otherwise you will get
-the following HTTP response during the authentication flow:&lt;/p>
-&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-http" data-lang="http">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a40000">error=invalid_request&amp;amp;error_description=Missing parameter: code_challenge_method
-&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h5 id="device-code-grant">Device Code Grant&lt;/h5>
-&lt;p>If you are using a confidential client with the Device Code grant, please make
-sure that the &lt;code>client_secret&lt;/code> is present in the request to the Device Code
-Endpoint either as HTTP Basic or HTTP POST parameter (see
-&lt;a href="#1-device-authorization-request">Device Authorization Request&lt;/a>).&lt;/p>
-&lt;h5 id="token-exchange-grant">Token Exchange Grant&lt;/h5>
-&lt;p>If you are using the Token Exchange grant, please make sure that the &lt;code>audience&lt;/code>
-(Optional) defines the logical name of the service that the token will be used
-for; when specified, it must match the client ID of a client registered in
-Check-in otherwise an &lt;code>invalid_client&lt;/code> error is returned
-(&lt;code>&amp;quot;description&amp;quot;: &amp;quot;audience not found&amp;quot;&lt;/code>)&lt;/p>
-&lt;h5 id="client-credentials-grant">Client Credentials Grant&lt;/h5>
-&lt;p>If you are using the Client Credentials grant, there is a minor change in the
-responses from UserInfo and Introspection Endpoints. The &lt;strong>Client ID&lt;/strong> of the
-client is &lt;strong>not&lt;/strong> released as the &lt;code>sub&lt;/code> claim any more and has replaced with by
-the &lt;code>client_id&lt;/code> claim. The &lt;code>sub&lt;/code> contains the identifier of the client which is
-unique, non-reassignable and scoped &lt;code>@egi.eu&lt;/code>.&lt;/p>
-&lt;h5 id="obtain-refresh-tokens">Obtain Refresh Tokens&lt;/h5>
-&lt;p>If you have obtained an Refresh Token from EGI Check-in Token Portal or
-oidc-agent issued by the MITREid Connect instance, you will need to replace them
-by creating new Refresh Tokens issued by Keycloak.&lt;/p>
-&lt;ul>
-&lt;li>
-&lt;p>If you have obtained Refresh Tokens using the EGI Check-in Token Portal,
-please check the following table:&lt;/p>
-&lt;table>
-&lt;thead>
-&lt;tr>
-&lt;th>Environment&lt;/th>
-&lt;th>URL&lt;/th>
-&lt;/tr>
-&lt;/thead>
-&lt;tbody>
-&lt;tr>
-&lt;td>Production&lt;/td>
-&lt;td>&lt;a href="https://aai.egi.eu/token">https://aai.egi.eu/token&lt;/a>&lt;/td>
-&lt;/tr>
-&lt;tr>
-&lt;td>Demo&lt;/td>
-&lt;td>&lt;a href="https://aai-demo.egi.eu/token">https://aai-demo.egi.eu/token&lt;/a>&lt;/td>
-&lt;/tr>
-&lt;tr>
-&lt;td>Development&lt;/td>
-&lt;td>&lt;a href="https://aai-dev.egi.eu/token">https://aai-dev.egi.eu/token&lt;/a>&lt;/td>
-&lt;/tr>
-&lt;/tbody>
-&lt;/table>
-&lt;/li>
-&lt;li>
-&lt;p>If you have obtained Refresh Tokens using the oidc-agent, please use the
-following command:&lt;/p>
-&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-shell" data-lang="shell">&lt;span style="display:flex;">&lt;span>$ oidc-gen --pub --issuer &amp;lt;ISSUER&amp;gt; --scope ...
-&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>
-&lt;div class="alert alert-info" role="alert">
-&lt;h4 class="alert-heading">Note&lt;/h4>
-You can find the &lt;code>ISSUER&lt;/code> in the
-&lt;a href="#endpoints">Endpoints&lt;/a> table.
-&lt;/div>
-&lt;/li>
-&lt;/ul>
-&lt;h4 id="common-issues">Common issues&lt;/h4>
+&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h4 id="common-issues">Common issues&lt;/h4>
 &lt;h5 id="error-messages-referring-to-missing-code_challenge-code_challenge_method-or-code_verifier-http-parameter">Error messages referring to missing &lt;code>code_challenge&lt;/code>, &lt;code>code_challenge_method&lt;/code> or &lt;code>code_verifier&lt;/code> HTTP parameter&lt;/h5>
 &lt;p>If you get error messages containing the PKCE HTTP parameters, probably the PKCE
 mode is enabled in your Service Configuration but the Application is not
@@ -2448,31 +2345,58 @@ in the vhost configuration:&lt;/p>
 &lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-nginx" data-lang="nginx">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#204a87;font-weight:bold">proxy_buffers&lt;/span> &lt;span style="color:#0000cf;font-weight:bold">4&lt;/span> &lt;span style="color:#0000cf;font-weight:bold">256k&lt;/span>&lt;span style="color:#000;font-weight:bold">;&lt;/span>
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#204a87;font-weight:bold">proxy_buffer_size&lt;/span> &lt;span style="color:#0000cf;font-weight:bold">128k&lt;/span>&lt;span style="color:#000;font-weight:bold">;&lt;/span>
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#204a87;font-weight:bold">proxy_busy_buffers_size&lt;/span> &lt;span style="color:#0000cf;font-weight:bold">256k&lt;/span>&lt;span style="color:#000;font-weight:bold">;&lt;/span>
-&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="integrating-science-gateways-with-rcauth-for-obtaining-proxy-certificates">Integrating Science Gateways with RCauth for obtaining (proxy) certificates&lt;/h2>
+&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h5 id="size-of-the-tokens">Size of the Tokens&lt;/h5>
+&lt;p>The size of an Access Token is around 1400 characters, depending on the
+information (claims) included in the payload of the JWT. So make sure that
+your OIDC implementation can handle large Tokens.&lt;/p>
+&lt;h5 id="token-introspection-errors">Token Introspection errors&lt;/h5>
+&lt;p>The Token Introspection is available to all the clients that are using any
+authentication method (&lt;code>client_secret_basic&lt;/code>, &lt;code>client_secret_post&lt;/code>,
+&lt;code>client_secret_jwt&lt;/code> or &lt;code>private_key_jwt&lt;/code>) (Confidential Clients) to the Token
+Endpoint. Public Clients (clients that do not use any authentication method)
+will not be able to get a successful response from the Introspection Endpoint.&lt;/p>
+&lt;h5 id="pkce-errors">PKCE errors&lt;/h5>
+&lt;p>If you are &lt;strong>not&lt;/strong> using PKCE (Proof Key for Code Exchange), please make sure to
+&lt;strong>disable&lt;/strong> the &amp;ldquo;PKCE Code Challenge Method&amp;rdquo; in the Service configuration in
+&lt;a href="https://aai.egi.eu/federation">EGI Federation Registry&lt;/a>, otherwise you will get
+the following HTTP response during the authentication flow:&lt;/p>
+&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-http" data-lang="http">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a40000">error=invalid_request&amp;amp;error_description=Missing parameter: code_challenge_method
+&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h5 id="device-code-grant">Device Code Grant&lt;/h5>
+&lt;p>If you are using a confidential client with the Device Code grant, please make
+sure that the &lt;code>client_secret&lt;/code> is present in the request to the Device Code
+Endpoint either as HTTP Basic or HTTP POST parameter (see
+&lt;a href="#1-device-authorization-request">Device Authorization Request&lt;/a>).&lt;/p>
+&lt;h5 id="token-exchange-grant">Token Exchange Grant&lt;/h5>
+&lt;p>If you are using the Token Exchange grant, please make sure that the &lt;code>audience&lt;/code>
+(Optional) defines the logical name of the service that the token will be used
+for; when specified, it must match the client ID of a client registered in
+Check-in otherwise an &lt;code>invalid_client&lt;/code> error is returned
+(&lt;code>&amp;quot;description&amp;quot;: &amp;quot;audience not found&amp;quot;&lt;/code>)&lt;/p>
+&lt;h2 id="integrating-science-gateways-with-rcauth-for-obtaining-proxy-certificates">Integrating Science Gateways with RCauth for obtaining (proxy) certificates&lt;/h2>
 &lt;p>In order for Science Gateways (VO portals) to obtain RFC proxy certificates
 derived from &lt;strong>personal&lt;/strong> end-entity certificates, an EGI Science Gateway can
 make use of the IGTF-approved IOTA-type RCauth.eu online CA. The actual
 integration goes via an intermediary service, called a Master Portal. EGI is
 running two Master Portal instances, one development, one production instance.&lt;/p>
-&lt;ul class="nav nav-tabs" id="tabs-28" role="tablist">
+&lt;ul class="nav nav-tabs" id="tabs-26" role="tablist">
 &lt;li class="nav-item">
 &lt;a class="nav-link active"
-id="tabs-28-0-tab" data-toggle="tab" href="#tabs-28-0" role="tab"
-aria-controls="tabs-28-0" aria-selected="true">
+id="tabs-26-0-tab" data-toggle="tab" href="#tabs-26-0" role="tab"
+aria-controls="tabs-26-0" aria-selected="true">
 Production
 &lt;/a>
 &lt;/li>
 &lt;li class="nav-item">
 &lt;a class="nav-link"
-id="tabs-28-1-tab" data-toggle="tab" href="#tabs-28-1" role="tab"
-aria-controls="tabs-28-1" aria-selected="false">
+id="tabs-26-1-tab" data-toggle="tab" href="#tabs-26-1" role="tab"
+aria-controls="tabs-26-1" aria-selected="false">
 Development
 &lt;/a>
 &lt;/li>
 &lt;/ul>
-&lt;div class="tabx-content" id="tabs-28-content">
+&lt;div class="tabx-content" id="tabs-26-content">
 &lt;div class="tab-pane show active"
-id="tabs-28-0" role="tabpanel" aria-labelled-by="tabs-28-0-tab">
+id="tabs-26-0" role="tabpanel" aria-labelled-by="tabs-26-0-tab">
 &lt;table>
 &lt;thead>
 &lt;tr>
@@ -2509,7 +2433,7 @@ id="tabs-28-0" role="tabpanel" aria-labelled-by="tabs-28-0-tab">
 &lt;/table>
 &lt;/div>
 &lt;div class="tab-pane "
-id="tabs-28-1" role="tabpanel" aria-labelled-by="tabs-28-1-tab">
+id="tabs-26-1" role="tabpanel" aria-labelled-by="tabs-26-1-tab">
 &lt;table>
 &lt;thead>
 &lt;tr>