An authorization failure reason is seen when Testimony detect a difference between a recording where a transaction was able to be run by the given user, but in the playback the same object cannot be run as the user is no longer authorized. Authorization messages and return-codes are the identifying markers which Testimony is looking for.

Example Scenario

A common scenario for use of this scenario in regression test cycles is when authorization changes are being introduced either knowingly or unknowingly. If there are hundreds or thousands of users to be managed and a rationalised list of common roles, then a small change to alter permissions can have a drastic effect on users once the change is promoted to production.


All authorization failures will be detected automatically by Testimony during the playback for all object types. When a failure is detected by Testimony in the playback, the last authorization failure for the given user is checked by the playback engine and its details stored.

The authorization failure report (known by the transaction name, SU53) can also be seen from the Investigation Screen by clicking on the failure message.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment