Merge pull request #8297 from harness/PL-56727

[PL-56727]: approle custom path documentation

docs/first-gen/firstgen-platform/security/secrets-management/add-a-hashi-corp-vault-secrets-manager.md

@@ -105,6 +105,20 @@ path "auth/token/renew-self"
 }
 ```
 
+#### Custom Authentication Path for AppRole Login
+
+:::note
+This feature is supported on delegate version `837xx` and above and is available behind the Feature Flag `PL_APPROLE_CUSTOM_PATH`. Contact [Harness Support](mailto:support@harness.io) to enable the feature.
+:::
+
+The `appRoleLogin` method now supports a custom authentication path, utilizing it if provided, or defaulting to the standard `approle` endpoint if not specified.
+
+![](./static/add-a-hashi-corp-vault-secrets-manager-68.png)
+
+For example, the custom AppRole path can be set as `<customPath>`, providing greater flexibility in configuring the authentication mechanism. This feature is particularly useful in scenarios where the default authentication path requires customization.
+
+Ensure that the custom AppRole path you configure exists in your HashiCorp Vault. This step is necessary for the authentication to succeed using the custom path.
+
 ### Option: Vault Agent
 
 To authenticate with Vault Agent, make sure you have configured it on the required environment, with entries for **method** and **sinks**. For more information, see [Vault Agent](https://www.vaultproject.io/docs/agent).