You experience issues such as the Amster export fails; potentially resulting in a 502 Bad Gateway error, you cannot list all the OAuth 2.0 clients in the console, or the list of OAuth 2.0 clients takes a long time to load in the console.
The following error is shown in the org.forgerock.openam.core.sms.SmsPasswordTransformer debug log when this happens:
org.forgerock.openam.core.sms.SmsPasswordTransformer:04/02/2020 01:22:06:161 PM GMT: Thread[http-nio-8080-exec-17,5,main]: TransactionId[314f2da7-9f14-45cb-a32b-073bc8a36672-4579068] No system property value for SMS_TRANSPORT_ENCRYPTION so using
Installed the Amster transport key.
The Amster transport key is required to allow encrypted passwords to be imported and exported. The documentation states that the transport key must be deleted after imports and exports have completed. However, if the transport key is not deleted, the processing time for any interfaces that list objects with passwords or secrets (such as an Amster export or listing OAuth 2.0 clients in the console) will be impacted and may lead to a timeout before the request completes, causing this error to occur.
This issue can be resolved by firstly removing the transport key. See Amster User Guide › To Delete a Transport Key for further information.
Additionally, in AM 5.5.2 and later, you can also increase the read-timeout when you connect to Amster using the -t (--connection-timeout) option. This timeout defaults to 10 seconds but you can increase it further if you are still seeing issues after removing the transport key. For example, the following --connection-timeout option will increase the timeout to 45 seconds:
am> connect --connection-timeout 45 --interactive http://host1.example.com:8080/openam