fixes

Author: lukaszsocha2

.github/ISSUE_TEMPLATE/config.yml

@@ -4,7 +4,7 @@ contact_links:
     url: https://github.com/box/box-java-sdk/tree/combined-sdk/docs
     about: Before creating an issue, I have checked that the SDK documentation doesn't solve my issue.
   - name: API documentation
-    url: https://developer.box.com/guides/
+    url: https://developer.box.com/guides
     about: Before creating an issue, I have checked that the API documentation doesn't solve my issue.
   - name: Box Developer Forums
     url: https://community.box.com/box-platform-5

.github/ISSUE_TEMPLATE/question.md

@@ -43,6 +43,6 @@ Java SDK: <!-- Replace with the version of the Java SDK you're using. -->
 Java: <!-- Replace with the version of Java your application is running on. -->
 
 [sdk-docs]: ./docs
-[api-docs]: https://developer.box.com/guides/
+[api-docs]: https://developer.box.com/guides
 [dev-forums]: https://community.box.com/box-platform-5
 [github-repo]: https://github.com/box/box-java-sdk/search?type=Issues

README.md

@@ -292,20 +292,30 @@ that are NOT compatible with FIPS 140-2 validated cryptographic library (`org.bo
 There are two ways of ensuring that decryption operation is FIPS-compiant.
 
 1. You can provide a custom implementation of the `IPrivateKeyDecryptor` interface, 
-which performs the decryption operation using FIPS-certified library of your choice. The interface requires the
-implementation of just one method:
+which performs the decryption operation using FIPS-certified library of your choice. 
+`IPrivateKeyDecryptor` interface is availiable both in `com.box.sdk` and `com.box.sdkgen` packages.
+The interface requires the implementation of just one method:
 ```java
 PrivateKey decryptPrivateKey(String encryptedPrivateKey, String passphrase);
 ```
-After implementing the custom decryptor, you need to set your custom decryptor class in the Box Config. 
-Below is an example of setting up a `BoxDeveloperEditionAPIConnection` with a config file and the custom decryptor.  
+After implementing the custom decryptor, you need to set your custom decryptor class:
+
+- For `com.box.sdk` package, you can set the custom decryptor in the `BoxConfig` object 
+before creating the `BoxDeveloperEditionAPIConnection`.
 ```java
 Reader reader = new FileReader(JWT_CONFIG_PATH);
 BoxConfig boxConfig = BoxConfig.readFrom(reader);
 boxConfig.setPrivateKeyDecryptor(customDecryptor);
 BoxDeveloperEditionAPIConnection api = BoxDeveloperEditionAPIConnection.getAppEnterpriseConnection(boxConfig);
 ```
 
+- For `com.box.sdkgen` package, you can set the custom decryptor in the `JWTConfig` object
+```java
+JWTConfig newConfig = JWTConfig.fromConfigFile(JWT_CONFIG_PATH, customDecryptor);
+BoxJWTAuth auth = new BoxJWTAuth(jwtConfig);
+BoxClient client = new BoxClient(auth);
+```
+
 2. Alternative method is to override the Bouncy Castle libraries to the v.1.57 version, 
 which are compatible with the FIPS 140-2 validated cryptographic library (`org.bouncycastle:bc-fips`).