Peeringhub.io Stir Shaken CA Service
  • Peeringhub STI-ACME Server
  • Guides
    • Stir/Shaken Compliance Guide
    • Q and A on STI Test Plan
      • STI-PA-TC-026
      • STI-PA-TC-021
      • STI-PA-TC-019
      • STI-PA-TC-024
      • STI-PA-TC-022
      • STI-PA-TC-025
    • Purchase Subscription
    • Generating Certificate
      • Web UI
        • Renew Stir/Shaken Certificate
      • ACME protocol reference
        • Protocol Overview
        • List server directory
        • Get nonce
        • Account creation & Authorization
        • Get ACME account status
        • Order a new certificate
        • List active orders
        • Key change
        • Account deactivation
      • Desktop Client
      • Windows Command Line Client
      • Linux Command Line Client
    • Staging Environment Support
      • Configuring ACME Client
    • Getting Support
    • Troubleshoot
    • Verify a Stir/Shaken Certificate
    • Peeringhub STI-API
      • Generate Auth Token
      • Generate Private Key
      • Extract Your Private Key
      • Generate Stir/Shaken Certifiate
    • FAQ
Powered by GitBook
On this page
  1. Guides
  2. Staging Environment Support

Configuring ACME Client

PreviousStaging Environment SupportNextGetting Support

Last updated 2 years ago

You can use the Peeringhub's ACME client in Peeringhub's Staging ACME server as well.

The same client software can be downloaded from:

The acme_config needs to be updated to the following:

#
# ACME client configuration
#

# ACME server URL
server_url    https://stica-dev.peeringhub.io/acme

# Public key ID
kid        ACME client test EC P-256 key

#
# Iconectiv configuration
#
pa_user_id        login
pa_password        password
pa_staging        true
pa_trace        false

# EOF

The pa_staging is set to "false" by default. If you want to use the ACME client in the staging environment, you must set as "true."

The pa_trace value is optional. It is "false" by default. If set to "true", then it will log all the HTTP interaction with iConnectiv.

https://github.com/peeringhub/RHEL-ACME-Cllient