Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-17743

Amster sms.transport.key causes perf issues when not removed

    XMLWordPrintable

    Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 6.5.3, 7.0.1
    • None
    • Amster, secrets
    • Rank:
      1|i04dwe:

      Description

      Bug description

      There are bugs already known when sms.transport.key is left in the Keystore however they have not been fixed but instead, we recommend removing the sms.transport.key after its use. This is not easy process actually (especially in CDM) and it's an AM bug.

      How to reproduce the issue

      1. Created 10 OAuth2 clients. Querying the OAuth2 clients via the UI loads as normal
      2. created the sms.transport.key using Amster's sample script: ./transport-key.sh generate /home/forgerock/openam2/openam
      3. restart AM
      4. first attempts in the Clients UI take 30-40s, after a while it drops to 10s
      5. remove the sms.transport.key using Amster's sample script:./transport-key.sh delete /home/forgerock/openam2/openam
      6. restart AM
      7. Querying the OAuth2 clients via the UI loads as normal
      Expected behaviour
      sms.transport.key shouldn't have any impact 
      
      Current behaviour
      if sms.transport.key is in the keystore, it affects Agents profile response time
      

      Work around

      The workaround is to remove it but this is not always an acceptable workaround as it requires an AM restart.

        Attachments

          Issue Links

            Activity

              People

              Unassigned Unassigned
              anastasios.kampas Anastasios Kampas
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: