SigningHub Admin

Make the following changes in the “appsettings.Production.json” file to configure Application Settings for SigningHub Admin Web.

---

To add the '00' IDD prefix (if not already present) in the mobile number:

"MODIFY_MOBILE_NUMBER_FOR_SAM": "true"

For the tag with the “MODIFY_MOBILE_NUMBER_FOR_SAM” key, set the value 'True” and SigningHub works as of today by adding the '00' prefix (if not already present) in the mobile number before sending it to the ADSS Server's SAM.

If it's “False”, SigningHub will send the mobile number to the ADSS's SAM without any modifications.

---

To disable Swagger documentation:

"EnableSwaggerDocumentation": "false"

Set the value of the EnableSwaggerDocumentation key to false (default) or omit the key to disable Swagger documentation for security reasons. To enable Swagger documentation, set the value of this key to true.

---

To use HashiCorp KeyVault:

"HASHI_CORP_UAMI_CLIENT_ID": "",
"HASHI_CORP_LOGIN_URL": "",
"HASHI_CORP_UAMI_NAME": "",
"HASHI_CORP_NAMESPACE": "",
"HASHI_CORP_VAULT_PATH": "",
"HASHI_CORP_SECRET_KEY": "",
"HASHI_CORP_SECRET_KEY_TYPE": "PASSWORD" <!--Possible Values: PASSWORD | CONNECTION_STRING-->

For the tag with the “HASHI_CORP_UAMI_CLIENT_ID” key, specify the unique identifier for the client application integrating with the HashiCorp Key Vault connector.

For the tag with the “HASHI_CORP_LOGIN_URL” key, specify the URL where the HashiCorp Vault can be accessed for authentication and authorisation.

For the tag with the “HASHI_CORP_UAMI_NAME” key, specify a unique identifier or label within Azure Active Directory (AD), used to identify and manage individual users or entities within the Azure AD framework, ensuring an organised and secure structure for user-related information and permissions.

For the tag with the “HASHI_CORP_NAMESPACE” key, specify the logical partition within HashiCorp Vault for organising and managing secrets.

For the tag with the “HASHI_CORP_VAULT_PATH” key, specify a pathway to a location within the HashiCorp Vault for storing and managing secrets and data.

For the tag with the “HASHI_CORP_SECRET_KEY” key, specify the key against which to get the value from the Key Vault.

For the tag with the “HASHI_CORP_SECRET_KEY_TYPE” key, possible values are password and connection string.

For the above tags, add the relevant details of the HashiCorp KeyVault to integrate SigningHub with HashiCorp KeyVault to securely access sensitive information, such as secrets stored within HashiCorp KeyVault. If it's empty, then SigningHub will work without the HashiCorp KeyVault integration.