EGI-Federation · gwarf · Mar 10, 2023 · Nov 11, 2022 · Nov 11, 2022 · Nov 11, 2022
@@ -58,10 +58,19 @@
       "pattern": "^https://opensource.org/licenses"
     },
     {
-      "pattern": "^https://servproject.i3m.upv.es/ec3-ltos/index.php"
+      "pattern": "^https://servproject.i3m.upv.es/ec3-ltos/*"
     },
     {
       "pattern": "^https://operations-portal.egi.eu/downtimes/subscription"
+    },
+    {
+      "pattern": "^https://operations-portal.egi.eu/vo"
+    },
+    {
+      "pattern": "^https://github.com/.*.keys"
+    },
+    {
+      "pattern": "^https://tools.ietf.org/html/rfc*"
     }
   ]
 }
@@ -16,7 +16,7 @@ weight: 20
 - When introducing services, link to the public page of the service, if any:
 
 ```markdown
-[EGI Cloud Compute](https://www.egi.eu/services/cloud-compute/)
+[EGI Cloud Compute](https://www.egi.eu/service/cloud-compute/)
 ```
 
 ## Markdown writing guidelines

@@ -17,7 +17,7 @@ description: "EGI Accounting identity card"
 | Support Email                           | `apel-admins` `<at>` `stfc.ac.uk`                                                                                                                 |
 | [Helpdesk](../../helpdesk) Support Unit | **EGI Services and Service Components** <br/> I\_\_ Accounting Portal <br/> I\_\_ APEL Client and Accounting Repository                           |
 | Configuration Database entries          | [Repository](https://goc.egi.eu/portal/index.php?Page_Type=Site&id=237) <br/> [Portal](https://goc.egi.eu/portal/index.php?Page_Type=Site&id=646) |
-| Suppliers                               | [UKRI](https://www.ukri.org/) (Repository), [CESGA](http://www.cesga.es) (Portal)                                                                 |
+| Suppliers                               | [UKRI](https://www.ukri.org/) (Repository), [CESGA](https://www.cesga.es) (Portal)                                                                |
 | Roadmap                                 | N/A                                                                                                                                               |
 | Release notes                           | N/A                                                                                                                                               |
 | Source code                             | [APEL](https://github.com/apel/apel), Portal: N/A                                                                                                 |

@@ -77,6 +77,6 @@ will be assigned to the groups when they create the account.
 
 ## Documentation
 
-- [Mailman documentation](http://www.gnu.org/software/mailman/docs.html)
+- [Mailman documentation](https://www.gnu.org/software/mailman/docs.html)
 - [Mailman Frequently Asked Questions](https://wiki.list.org/DOC/Frequently%20Asked%20Questions)
 - [List administrator tasks](https://wiki.list.org/DOC/3%20List%20administrator%20tasks)
@@ -12,9 +12,9 @@ Use this section to get started quickly with internal EGI services:
   insight into how EGI is able to offer advanced public cloud services
 - The [**Configuration Database**](https://goc.egi.eu) records the topology
   of the sites in the EGI federation
-- [**Service Monitoring**](http://argo.egi.eu) tracks and controls the
+- [**Service Monitoring**](https://argo.egi.eu) tracks and controls the
   performance of the services
 - [**Accounting**](https://accounting.egi.eu) tracks service and resource
   usage, providing insights and reports on consumption
-- The [**Helpdesk**](http://helpdesk.egi.eu) lets users and providers report
+- The [**Helpdesk**](https://helpdesk.egi.eu) lets users and providers report
   incidents and bugs, or request changes
@@ -8,7 +8,7 @@ description: >
 
 ## What is it?
 
-The [EGI Service Monitoring](http://argo.egi.eu) **keeps an eye on the
+The [EGI Service Monitoring](https://argo.egi.eu) **keeps an eye on the
 performance of the EGI services** to quickly detect and resolve issues.
 
 The service monitors the infrastructure by collecting data generated by

diff --git a/content/en/providers/check-in/idp/_index.md b/content/en/providers/check-in/idp/_index.md
@@ -6,7 +6,7 @@ type: "docs"
 ---
 
 This page contains information about integrating your identity provider (IdP)
-with [Check-in](https://www.egi.eu/services/check-in/) in order to allow users
+with [Check-in](https://www.egi.eu/service/check-in/) in order to allow users
 in your community to access EGI tools and services.
 
 Organisations who want to register their IdP in Check-in needs to fill this

@@ -6,7 +6,7 @@ type: "docs"
 ---
 
 This page contains information about connecting services to
-[EGI Check-in](https://www.egi.eu/services/check-in/) in order to allow user
+[EGI Check-in](https://www.egi.eu/service/check-in/) in order to allow user
 login through Check-in and to receive users' attributes. Check-in is connected
 to a wide range of academic and social Identity Providers that users can choose
 from in order to access your service.
@@ -102,7 +102,7 @@ The integration follows a two-step process:
 EGI Check-in supports two authentication and authorisation protocols that you
 can choose from:
 
-1. [Security Assertion Markup Language (SAML) 2.0](http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html)
+1. [Security Assertion Markup Language (SAML) 2.0](https://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html)
 1. [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html) - an
    extension to [OAuth 2.0](https://tools.ietf.org/html/rfc6749)
 
@@ -274,7 +274,7 @@ If the SP supports the Single Logout profile, then its metadata **MUST** contain
 - at least one `<md:SingleLogoutService>` endpoint element (this MAY be omitted
   if the SP solely issues `<samlp:LogoutRequest>` messages containing the
   `<aslo:Asynchronous>` extension
-  [SAML2ASLO](http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-cs01.pdf))
+  [SAML2ASLO](https://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-cs01.pdf))
 
 ### Attributes
 
@@ -325,7 +325,7 @@ Service Providers can be integrated with EGI Check-in using OpenID Connect
 (OIDC) as an alternative to the SAML2 protocol. To allow this, the EGI Check-in
 IdP provides an OpenID Connect (OAuth2) API based on
 [Keycloak](https://www.keycloak.org), which has been
-[certified by the OpenID Foundation](http://openid.net/certification/).
+[certified by the OpenID Foundation](https://openid.net/certification/).
 Interconnection with the EGI Check-in OpenID Provider allows users to sign in
 using any of the supported backend authentication mechanisms, such as
 institutional IdPs registered with eduGAIN or Social Providers. Once the user
@@ -1927,7 +1927,7 @@ Identity Assurance, which is conveyed to the SP through both the
 (`AuthnContextClassRef`) of the SAML authentication response. EGI Check-in uses
 Assurance Profiles which distinguish between three Identity Assurance levels,
 similarly to the
-[eID Assurance Framework (eIDAF)](http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:JOL_2015_235_R_0002).
+[eID Assurance Framework (eIDAF)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:JOL_2015_235_R_0002).
 Each level is represented by a URI as follows:
 
 - **Low**: Authentication through a social identity provider or other low

@@ -9,7 +9,7 @@ description: >
 This manual provides information on how to set up a Resource Centre providing
 cloud resources in the EGI infrastructure. Integration with FedCloud requires a
 _working OpenStack installation_ as a pre-requirement. EGI supports any recent
-[OpenStack version](http://releases.openstack.org) (tested from OpenStack
+[OpenStack version](https://releases.openstack.org) (tested from OpenStack
 Mitaka).
 
 EGI expects the following OpenStack services to be available and accessible from

@@ -18,7 +18,7 @@ ssmsend every six hours.
 
 ### Using the VM Appliance
 
-[cASO configuration](http://caso.readthedocs.org/en/latest/configuration.html)
+[cASO configuration](https://caso.readthedocs.org/en/latest/configuration.html)
 is stored at `/etc/caso/caso.conf`. Most default values should be OK, but you
 must set:
 
@@ -29,7 +29,7 @@ must set:
 
 - credentials to access the accounting data (lines 28-47, more options also
   available). Check the
-  [cASO documentation](http://caso.readthedocs.org/en/latest/configuration.html#openstack-configuration)
+  [cASO documentation](https://caso.readthedocs.org/en/latest/configuration.html#openstack-configuration)
   for the expected permissions of the user configured here.
 
 - The mapping from EGI VOs to your local projects `/etc/caso/voms.json`,

@@ -42,5 +42,5 @@ Extra checks for your installation:
   [site certification manual tests](../../../providers/operations-manuals/howto04_site_certification_manual_tests/#check-the-functionality-of-the-cloud-elements)
   against your endpoints.
 
-- Check in the [accounting portal](http://accounting.egi.eu/) that your site is
+- Check in the [accounting portal](https://accounting.egi.eu/) that your site is
   listed and the values reported look consistent with the usage of your site.
@@ -10,7 +10,7 @@ description: "Using Storage Accounting Record (StAR)"
 Storage space usage accounting is based on the StAR (Storage Accounting Record)
 developed during the EMI project in conjunction with the OGF Usage Record Work
 Group (UR-WG). The format is documented
-[in GFD-I.201](http://cds.cern.ch/record/1452920/files/GFD.201.pdf).
+[in GFD-I.201](https://cds.cern.ch/record/1452920/files/GFD.201.pdf).
 
 EMI delivered StAR solutions for dCache and DPM in EMI-3. In both cases the
 storage service queries its database at a site and extracts data to populate
@@ -130,5 +130,5 @@ The page is updated on a daily basis.
 ## Storage Accounting Data at the EGI Accounting Portal
 
 The storage accounting view is currently available on the
-[development instance](http://accounting-devel.egi.eu/storage.php) of the
+[development instance](https://accounting-devel.egi.eu/storage.php) of the
 Accounting Portal.
@@ -42,7 +42,7 @@ in parallel):
   Management Database (CMDB)
 - Information System: evaluating if the new technology should publish
   information in the Information System according to the
-  [GLUE Schema](http://www.ogf.org/documents/GFD.147.pdf).
+  [GLUE Schema](https://www.ogf.org/documents/GFD.147.pdf).
 - [Monitoring](../../../internal/monitoring): the new technology should allow
   external monitoring. If particular aspects of the technology need to be
   monitored, specific monitoring probes should be provided by the TPs and

@@ -15,7 +15,7 @@ SPEC, a new CPU benchmark that will replace si2k and will become the reference
 benchmark for accounting purposes.
 
 Detailed description of the reasons are provided on the
-[transition to a new CPU benchmarking unit for the WLCG](http://indico.cern.ch/getFile.py/access?contribId=3&sessionId=0&resId=0&materialId=0&confId=49388).
+[transition to a new CPU benchmarking unit for the WLCG](https://indico.cern.ch/getFile.py/access?contribId=3&sessionId=0&resId=0&materialId=0&confId=49388).
 
 ### Q2: What is HEP SPEC 06?
 
@@ -36,7 +36,7 @@ change.
 ### Q3: Where can I find information about HEP SPEC 06 measurements?
 
 Some example results are available on the
-[HEPIX group-page](http://w3.hepix.org/benchmarking.html), where one can see the
+[HEPIX group-page](https://w3.hepix.org/benchmarking.html), where one can see the
 differences between gcc3.4.x and gcc4.1.x.
 
 Additional results tables are available from various EGI partners:

@@ -9,7 +9,7 @@ To ensure interoperability within and outside of EGI, the
 [Policy on Acceptable Authentication Assurance](https://documents.egi.eu/document/2930)
 defined a common set of trust anchors (in a PKIX implementation "Certification
 Authorities") that all sites in EGI should install. In short, all CAs accredited
-to the [Interoperable Global Trust Federation](http://www.igtf.net/) under the
+to the [Interoperable Global Trust Federation](https://www.igtf.net/) under the
 [classic](https://www.igtf.net/ap/classic/),
 [MICS](https://www.igtf.net/ap/mics/) or [SLCS](https://www.igtf.net/ap/slcs/)
 _Authentication Profiles_ are approved for use in EGI. When installing the
@@ -25,7 +25,7 @@ exception.
 ## Release notes
 
 Review the
-[release notes](http://repository.egi.eu/sw/production/cas/1/current/README.txt)
+[release notes](https://repository.egi.eu/sw/production/cas/1/current/README.txt)
 containing important notices about the current release, as well as a list of
 changes to the trust fabric.
 
@@ -37,7 +37,7 @@ to manage the installation. To install the currently valid distribution, all RPM
 packages are provided at
 
 ```text
-http://repository.egi.eu/sw/production/cas/1/current/
+https://repository.egi.eu/sw/production/cas/1/current/
 ```
 
 The current version is based on the
@@ -49,14 +49,14 @@ trusted CAs.
 ### Using YUM package management
 
 Add the following
-[repo-file](http://repository.egi.eu/sw/production/cas/1/current/repo-files/EGI-trustanchors.repo)
+[repo-file](https://repository.egi.eu/sw/production/cas/1/current/repo-files/EGI-trustanchors.repo)
 to the `/etc/yum.repos.d/` directory:
 
 ```ini
 [EGI-trustanchors]
 name=EGI-trustanchors
-baseurl=http://repository.egi.eu/sw/production/cas/1/current/
-gpgkey=http://repository.egi.eu/sw/production/cas/1/GPG-KEY-EUGridPMA-RPM-3
+baseurl=https://repository.egi.eu/sw/production/cas/1/current/
+gpgkey=https://repository.egi.eu/sw/production/cas/1/GPG-KEY-EUGridPMA-RPM-3
 gpgcheck=1
 enabled=1
 ```
@@ -65,7 +65,7 @@ and then update your installation. How to update depends on your previous
 activity:
 
 - **if you have previously ever installed the `lcg-CA` package**, remove any
-  references to `http://linuxsoft.cern.ch/LCG-CAs/current` from your YUM setup,
+  references to `https://linuxsoft.cern.ch/LCG-CAs/current` from your YUM setup,
   and run
 
 ```shell
@@ -116,7 +116,7 @@ $ wget -q -O - \
 
 ```shell
 #### EGI Trust Anchor Distribution ####
-deb http://repository.egi.eu/sw/production/cas/1/current egi-igtf core
+deb https://repository.egi.eu/sw/production/cas/1/current egi-igtf core
 ```
 
 - Populate the cache and install the meta-package
@@ -134,7 +134,7 @@ review the release notes carefully for any security issues or withdrawn CAs. The
 tar files can be found in the EGI repository at
 
 ```text
-http://repository.egi.eu/sw/production/cas/1/current/tgz/
+https://repository.egi.eu/sw/production/cas/1/current/tgz/
 ```
 
 Once you have downloaded the directory, you can unpack all the CA tar,gz as
@@ -153,20 +153,20 @@ Quattor templates are povided as drop-in replacements for both QWG and CDB
 installations. Update your software repository (re-generating the repository
 templates as needed) and obtain the new CA templates from:
 
-- `http://repository.egi.eu/sw/production/cas/1/current/meta/ca-policy-egi-core.tpl`
+- `https://repository.egi.eu/sw/production/cas/1/current/meta/ca-policy-egi-core.tpl`
   for QWG
-- `http://repository.egi.eu/sw/production/cas/1/current/meta/pro_software_meta_ca_policy_egi_core.tpl`
+- `https://repository.egi.eu/sw/production/cas/1/current/meta/pro_software_meta_ca_policy_egi_core.tpl`
   for CDB
 
 Make sure to mirror (or refer to) the new repository at
-`http://repository.egi.eu/sw/production/cas/1/current/` and create the
+`https://repository.egi.eu/sw/production/cas/1/current/` and create the
 appropriate repository definition file.
 
 For WLCG sites that are migrating from the lcg-CA package: the WLCG policy
 companion of the EGI templates can be found at
-[QWG](http://lcg-ca.web.cern.ch/lcg-ca/distribution/current/meta/ca-policy-lcg.tpl)
+[QWG](https://lcg-ca.web.cern.ch/lcg-ca/distribution/current/meta/ca-policy-lcg.tpl)
 and
-[CDB](http://lcg-ca.web.cern.ch/lcg-ca/distribution/current/meta/pro_software_meta_ca_policy_lcg.tpl)
+[CDB](https://lcg-ca.web.cern.ch/lcg-ca/distribution/current/meta/pro_software_meta_ca_policy_lcg.tpl)
 and can be included in the profile in parallel with the EGI core template. All
 packages needed are also included in the EGI repository, so only a single
 repository reference is necessary.
@@ -230,4 +230,4 @@ or its [mirror](https://www.apgridpma.org/distribution/). See the IGTF and
 EUGridPMA web pages for additional information.
 
 Make sure to verify your trust anchors with [TACAR](https://www.tacar.org/), the
-[TERENA](http://www.terena.org) Academic CA Repository, where applicable.
+[TERENA](https://www.terena.org) Academic CA Repository, where applicable.
diff --git a/...en/providers/operations-manuals/howto03_site_certificatoin_giis_check/_index.md b/...en/providers/operations-manuals/howto03_site_certificatoin_giis_check/_index.md
@@ -20,7 +20,7 @@ These are the main branches of the LDAP tree:
 - `GlueServiceUniqueID`
 
 It is recommended to use the
-[Apache Studio LDAP browser](http://directory.apache.org/studio/), although in
+[Apache Studio LDAP browser](https://directory.apache.org/studio/), although in
 this page `ldapsearch` queries are shown.
 
 ### Contact information

@@ -97,11 +97,11 @@ administrator.
 
 ### DNS round robin load balancing
 
-- [Load balancing](http://en.wikipedia.org/wiki/Load_distribution) is a
+- [Load balancing](https://en.wikipedia.org/wiki/Load_distribution) is a
   technique to distribute workload evenly across two or more resources. A load
   balancing method, which does not necessarily require a dedicated software or
   hardware node, is called
-  [round robin DNS](http://en.wikipedia.org/wiki/Round-robin_DNS).
+  [round robin DNS](https://en.wikipedia.org/wiki/Round-robin_DNS).
 
 - We can assume that all transactions (queries to top or site BDII generate the
   same resource load. For an effective load balancing, all top or site BDII
@@ -112,7 +112,7 @@ administrator.
   is a primary DNS server (`dns.domain.tld`) where the DNS load balancing will
   be implemented, one simply has to add multiple A records mapping the same
   hostname to multiple IP addresses under the core.top.domain
-  [DNS zone](http://en.wikipedia.org/wiki/DNS_zone). It is equally applicable to
+  [DNS zone](https://en.wikipedia.org/wiki/DNS_zone). It is equally applicable to
   site BDII.
 
 ```bind

@@ -54,11 +54,11 @@ Database entries.
 4. Stunnel uses Public-key cryptography with X.509 digital certificates to
    secure the SSL connection. Clients can optionally be authenticated via a
    certificate too
-5. For more references, please check [www.stunnel.org](http://www.stunnel.org/)
+5. For more references, please check [www.stunnel.org](https://www.stunnel.org/)
 
 - There are other possibilities for encryption, like enabling SSL Support
   directly in MySQL, but these approach was not tested. Details can be obtained
-  [here](http://www.howtoforge.com/how-to-set-up-mysql-database-replication-with-ssl-encryption-on-centos-5.4).
+  [here](https://www.howtoforge.com/how-to-set-up-mysql-database-replication-with-ssl-encryption-on-centos-5.4).
 
 ## MySQL replication
 

@@ -83,7 +83,7 @@ ARC uses its own system to publish the accounting data through AMS, so please
 refer to the NorduGrid ARC 6 documentation:
 
 - Information relevant only for 6.4 ARC releases and beyond:
-  [Accounting-NG](http://www.nordugrid.org/documents/arc6/tech/accounting/accounting-ng.html#accounting-ng-tech)
+  [Accounting-NG](https://www.nordugrid.org/documents/arc6/tech/accounting/accounting-ng.html#accounting-ng-tech)
 - The old ActiveMQ network was dismissed.
   [ARC 6.12](https://www.nordugrid.org/arc/releases/6.12/release_notes_6.12.html)
   introduces new settings for publishing the accounting records via AMS.
@@ -95,4 +95,4 @@ as explained in the general information section. In addition, HTCondor-CE must
 be configured to create accounting records:
 
 - Information on configuring HTCondor-CE for APEL accounting:
-  [APEL Accounting for HTCondor-CE](../../high-throughput-compute/htcondor-ce-apel)
+  [APEL Accounting for HTCondor-CE](../../high-throughput-compute/htcondor-ce-accounting)