Update configuration.md

Author: bhillkeyfactor

docsource/configuration.md

@@ -1,9 +1,9 @@
 ## Overview
 
-HydrantId operates a PKI-as-a-service platform for customers around the globe. The AnyGateway solution for HydrantId allows Keyfactor Command to perform:
+HID operates a PKI-as-a-service platform for customers around the globe. The AnyGateway solution for HID allows Keyfactor Command to perform:
 
 - **CA Sync**:
-  - Download all certificates issued by connected Enterprise-tier CAs in HydrantId (full sync).
+  - Download all certificates issued by connected Enterprise-tier CAs in HID (full sync).
 - **Certificate Enrollment**:
   - Support certificate enrollment (new keys/certificate).
   - Intelligent handling of Renewal vs Reissue based on certificate expiration.
@@ -14,13 +14,13 @@ HydrantId operates a PKI-as-a-service platform for customers around the globe. T
 
 ## Requirements
 
-### 🔐 HydrantID API Key Setup Guide
+### 🔐 HID API Key Setup Guide
 
-This guide explains how to generate and use an API Key ID and Secret in HydrantID for authenticated API access.
+This guide explains how to generate and use an API Key ID and Secret in HID for authenticated API access.
 
 #### 📍 Where to Find API Key Management
 
-1. **Log in** to your HydrantID instance.
+1. **Log in** to your HID instance.
    - Example: https://acm-stage.hydrantid.com
 2. Click your **user profile icon** (top right) and select **"Profile"**.
 3. In the **Profile** page, scroll to the section labeled `API Keys`.
@@ -40,7 +40,7 @@ This guide explains how to generate and use an API Key ID and Secret in HydrantI
 
 #### 🔐 Using the API ID and Key with HAWK
 
-HydrantID uses [HAWK Authentication](https://github.com/hueniverse/hawk) to secure its API.
+HID uses [HAWK Authentication](https://github.com/hueniverse/hawk) to secure its API.
 
 ##### Required Fields in Authorization Header:
 ```text
@@ -56,13 +56,13 @@ Each HTTP request dynamically constructs a HAWK header using:
 
 ### Root CA Configuration
 
-Both the Keyfactor Command and AnyCA Gateway REST servers must trust the root CA, and any applicable intermediate CAs for HydrantID.
+Both the Keyfactor Command and AnyCA Gateway REST servers must trust the root CA, and any applicable intermediate CAs for HID.
 
 ---
 
 ## Gateway Registration
 
-The Gateway Registration tab configures the root or issuing CA certificate for the respective CA in HydrantId.  
+The Gateway Registration tab configures the root or issuing CA certificate for the respective CA in HID.  
 The certificate selected here should match the issuing CA identified in the [Root CA Configuration](#root-ca-configuration) step.
 
 ---
@@ -75,7 +75,7 @@ Naming Recommendations:
 - Each Certificate Profile should be named after its Product ID.
 
 Behavior:
-- The plugin maps HydrantID Policy Names directly to Product IDs in the Gateway Portal.
+- The plugin maps HID Policy Names directly to Product IDs in the Gateway Portal.
 
 Example:
 | HID Template | Product ID |
@@ -94,7 +94,7 @@ Selecting "Default" bypasses specifying a template.
 All certificate enrollment operations are submitted as "new" requests. However, the plugin supports intelligent handling:
 
 - **New Enrollment**:
-  - Submits a new CSR against the selected HydrantId Policy.
+  - Submits a new CSR against the selected HID Policy.
 - **Renewal vs Reissue**:
   - Uses the prior certificate's serial number (`PriorCertSN`) to retrieve the existing certificate.
   - Compares the expiration date against the current time.
@@ -121,15 +121,15 @@ The plugin uses the `/api/v2/certificates` endpoint to perform full synchronizat
 - **Certificate Parsing**:
   - PEM chains are split into individual certificates.
 
-> Note: HydrantId's API does not allow filtering certificates by CA, so all certificates from the tenant are synced.
+> Note: HID's API does not allow filtering certificates by CA, so all certificates from the tenant are synced.
 
 ## Certificate Revocation
 
 Revocation requests are sent via a PATCH to the `/api/v2/certificates/{id}` endpoint.
 
 **Mapped Revocation Reasons**:
 
-| Keyfactor Reason (RFC 5280) | HydrantID Reason |
+| Keyfactor Reason (RFC 5280) | HID Reason |
 |:---|:---|
 | 0 (Unspecified) | Unspecified |
 | 1 (KeyCompromise) | KeyCompromise |
@@ -144,7 +144,7 @@ Revocation requests are sent via a PATCH to the `/api/v2/certificates/{id}` endp
 
 ## Connection Information Validation
 
-The following fields are required when connecting the Gateway to HydrantId:
+The following fields are required when connecting the Gateway to HID:
 
 - `HydrantIdBaseUrl`
 - `HydrantIdAuthId`
@@ -156,11 +156,11 @@ Missing or empty fields will cause the plugin initialization to fail.
 
 # Additional Notes
 
-- After enrollment, the plugin polls HydrantId's `/csr/{id}/certificate` endpoint for up to **30 seconds** to retrieve the newly issued certificate.
+- After enrollment, the plugin polls HID's `/csr/{id}/certificate` endpoint for up to **30 seconds** to retrieve the newly issued certificate.
 - If the certificate is still unavailable, the enrollment will be marked **Pending** in Command and should be retried.
 - The plugin uses the Keyfactor standard logging infrastructure (`Keyfactor.Logging`).
 
 # 📌 Related Documentation
 
 - [HAWK Authentication Specification](https://github.com/hueniverse/hawk)
-- [HydrantID API Documentation](https://support.hydrantid.com/hc/en-us)
+- [HID API Documentation](https://support.hydrantid.com/hc/en-us)