Add some JSON as a reusable as a bug workaround (#55829)

Author: subatoi

content/actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-jfrog.md

@@ -35,12 +35,7 @@ For an example {% data variables.product.prodname_actions %} workflow using the
 
     For example, you can set `iss` to `https://token.actions.githubusercontent.com`, and the `repository` to something like "octo-org/octo-repo"`. This will ensure only Actions workflows from the specified repository will have access to your JFrog platform. The following is an example Claims JSON when configuring identity mappings.
 
-    ```json copy
-    {
-      "iss": "https://token.actions.githubusercontent.com",
-      "repository": "octo-org/octo-repo"
-    }
-    ```
+    {% data reusables.actions.jfrog-json-configuring-identity-mappings %}
 
 ## Adding the identity provider to JFrog
 

data/reusables/actions/jfrog-json-configuring-identity-mappings.md

@@ -0,0 +1,6 @@
+```json copy
+{
+    "iss": "https://token.actions.githubusercontent.com",
+    "repository": "octo-org/octo-repo"
+}
+```