Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
titleOpenAM Guidelines for logging Bugs

This document is to help you log bugs for the OpenAM project. Ensuring that you log the bug into the correct catagory and with the correct information will assist in the bug being fixed!

Is there a bug already filed?

Login to JIRA and check if there is a bug already filed for your issue. Use the Bugster search tool. If you cannot find anything that matches, then raise your own bug.

So how do I create a new issue?

You should create your issue in the OpenAM project and decide on the issue type:

  • Bug: Something is broken!
  • New Feature: You would really like OpenAM to do something new!
  • Task: Used to tasks that need to be completed, but are not specific issues.
  • Improvement: OpenAM does something already, but you have suggestion on how it can be done better!

Now you need to complete the new issue form.


A nice one line summary of the problem; eg: The ssoadm command does not work behind a load balancer.

Security Level

For issues that are not security related you can safely ignore this field. If you are raising a bug in the security category then please select forgerock_only. Please see the security bugs faq for more information.

  • Blocker: Blocks development and/or testing work, production could not run.
  • Critical: Crashes, loss of data, severe memory leak.
  • Major: Major loss of function.
  • Minor: Minor loss of function, or other problem where easy workaround is present.
  • Trivial: Cosmetic problem like misspelt words or misaligned text.
Due Date

Component owners will set a due date when the issue is reviewed.


Filing your issue under the correct category will ensure the issue will get reviewed and processed quickly. Please review the OpenAM issue component categories list for more information.

Affects Versions

Please select the version(s) of the product effected by the issue.

Fix Versions

Component owners will set a fix versions when the issue is reviewed.


This can be left at the default value unless otherwise stated by ForgeRock support or prior agreement.


Please fill in the following basic information:

  • OS Version: eg: CentOS 5
  • Container Version: eg: Tomcat 6.0.20
  • JVM Version: eg:
    Code Block
    # java -version
    java version "1.6.0"
    OpenJDK  Runtime Environment (build 1.6.0-b09)
    OpenJDK 64-Bit Server VM (build 1.6.0-b09, mixed mode)
  • OpenAM Version: eg: ForgeRock OpenAM Express Build 9(2010-February-07 13:29) You can get this from the Version button in the OpenAM console.

A detailed description of the issue. If you can reproduce the problem then the set of steps used to reproduce. If you have found a bug and located the source of the issue in the code, then feel free to paste in the code. If there is a lot of code then zip it up and attach it to the issue.