-
Type:
Bug
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 6.0.0
-
Component/s: scripting
-
Labels:
Bug description
A fix was given for bug . This works as expected until you enable message level logging and then authentication fails.OPENAM-12226
How to reproduce the issue
Details steps outlining how to recreate the issue (remove this text)
-
- Install AM 5.5.1
- Create DeviceMatch, DeviceSave and HOTP modules
- Install 27614-1 tpatch with fix
.OPENAM-12226 - Create a chain with all these modules, refer attached image
- Enable AM message level debugging
- 1st authentication: Invoke this chain: http://openam551.example.com:8989/openam/XUI/?realm=/employees#login/&authIndexType=service&authIndexValue=riskChain
- Perform datastore
- User challenged for HOTP
- Save device
- 2nd authentication: Invoke same chain again.
- Perform datastore
- User challenged for HOTP but user should not be challenged as we saved device in step 5 above
Expected behaviour
Authenticate correctly
Current behaviour
Authentication error
Work around
Dont use message level logging.
Code analysis
OPTIONAL - If you already investigated the code, please share your finding here (remove this text)
org.forgerock.$className.java
...
- is caused by
-
OPENAM-12226 Device Match - server side script fails
-
- Resolved
-
- is related to
-
OPENAM-13144 DeviceID Profiles are not saved
-
- Resolved
-