Centro stella dei pagamenti elettronici
  • Centro Stella
    • Instructions for Agenzia delle Entrate Mandate
      • How to join
        • 01. Sign the Agreement
        • 02. Integrate PagoPA Environments
          • Open routes
          • Request the mutual authentication certificates
          • Obtain an API key
          • Wait for activation email
          • Check if you are enabled for PagoPA UAT environment
        • 03. Configure the Batch Service
          • Prepare the Java KeyStore
          • Install the software
            • How to install JAR version
              • Download JAR file
              • Prepare the working directories
              • Define environment variables
            • How to install Docker version
              • Download Docker image
              • Define environment variables
              • Choose working directory to mount
          • Run the software
            • Run from JAR
            • Run with Docker
        • 04. Test and monitor integration
          • Test UAT
          • Test PROD
        • 05. Go live!
      • Releases / Changelog
        • Note regarding the modifications from 2.2.0 to 2.2.3
        • Note regarding the modifications from 2.1.2 to 2.2.0
        • Note regarding the modifications of the yaml file from 2.0.0 to 2.1.0
        • Note regarding the modifications of the yaml file from 1.5.1 to 2.0.0
        • Note regarding the modifications of the yaml file from 1.4.1 to 1.5.0
        • Note regarding the modifications of the yaml file from 1.3.2 to 1.4.1
        • Note regarding the modifications of the yaml file from 1.2.5 to 1.3.2
      • Appendixes
        • Appendix 1 - Environments
        • Appendix 2 - Input file specifications
        • Appendix 3 - AdE output file specifications
          • Appendix 3 - AdE output file specifications v1.2.5
        • Appendix 4 - AdE errors file specifications
        • Appendix 5 - Logback configuration
        • Appendix 6 - Configuration properties
        • Appendix 7 - Console log overview
        • Appendix 8 - Database connection for Spring Batch
        • Appendix 9 - FAQ & Troubleshooting
        • Appendix 10 - Python and Poetry installation
        • Appendix 11 - List of output and log files
      • Api Integration
  • Glossary
  • RTD documentation
    • Input file specifications
Powered by GitBook
On this page
  • Get cstar-cli tool
  • Step 1. Mutual Authentication certificate validity check UAT
  • Step 2. API Key validity check UAT
  1. Centro Stella
  2. Instructions for Agenzia delle Entrate Mandate
  3. How to join
  4. 02. Integrate PagoPA Environments

Check if you are enabled for PagoPA UAT environment

PreviousWait for activation emailNext03. Configure the Batch Service

Last updated 2 years ago

PagoPA provides a package of tools to test the environment integration and to run functional tests.

This paragraph describes how to test if you are able to call PagoPA APIs.

After the set up of the environments and after the Batch Service installation you will be required to run functional test using resources from the same package.

Get cstar-cli tool

Make sure to have the latest version downloaded.

  • download zip

    wget -O ./cstar-cli.tar.gz wget https://github.com/pagopa/cstar-cli/releases/latest/download/cstar-cli.tar.gz

  • decompress it

    tar -xvf cstar-cli.tar.gz

  • move to CSTAR-CLI directory

    cd cstar-cli-*

Step 1. Mutual Authentication certificate validity check UAT

The first step checks the validity of the client certificate, with a call to a dedicated using your certificate and your private key.

From the cstar-cli project root run the script with the following command:

sh ./integration_check/scripts/001-mAuth-check-UAT/script.sh /PATH/TO/COMPANY_NAME.certificate.pem /PATH/TO/COMPANY_NAME.key

Note that you have to specify the path to your certificate and to the private key as arguments.

The script will print the result, the correct value is 200 .

Example of expected result:

--<TIMESTAMP>--  https://api.uat.cstar.pagopa.it/rtd/mauth/check
Resolving api.uat.cstar.pagopa.it (api.uat.cstar.pagopa.it)... 20.86.233.151
Connecting to api.uat.cstar.pagopa.it (api.uat.cstar.pagopa.it)|20.86.233.151|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 24 [application/json]
Saving to: ‘STDOUT’
-
  "result": "PASS"
-

Step 2. API Key validity check UAT

From the cstar-cli project root run the script with the following command:

sh ./integration_check/scripts/002-API-key-check-UAT/script.sh /PATH/TO/COMPANY_NAME.certificate.pem /PATH/TO/COMPANY_NAME.key UAT_API_KEY

Note that you have to specify the path to your certificate, the path to the private key and the API key as arguments.

The script will print the result, the correct value is 200 .

Example of expected result:

--<TIMESTAMP>--  https://api.uat.cstar.pagopa.it/rtd/api-key/check
Resolving api.uat.cstar.pagopa.it (api.uat.cstar.pagopa.it)... 20.86.233.151
Connecting to api.uat.cstar.pagopa.it (api.uat.cstar.pagopa.it)|20.86.233.151|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 24 [application/json]
Saving to: ‘STDOUT’
-
  "result": "PASS"
-

The second step checks the validity of the API Key, with a call to a dedicated using your certificate, your private key and the UAT API Key.

endpoint
endpoint