Authentication Manager Bulk Admin (AMBA)

When an administrator tries to run an AMBA report using the LTIF command, the output does not show all available tokens.  In one case, an installation of 10,000 tokens only showed 717 token in the AMBA report.  Changing parameters to show all tokens regardless of type had no effect.

AMBA is not finding only 717 tokens; it is stopping when it runs across a token with corrupt or invalid data.  Enabling logging using the following...

./rsautil AMBulkAdmin --ini AMBA.ini -i amba_assigned_ltif.csv --searchlimit 50000 -r /tmp/output.csv --newlog -o /tmp/logfile.log

...the log file shows:

BOJ    : 2026-07-31 14:21:49 - 8.7.2.3.0 (1440892) - Input = amba_assigned_ltif.csv
Error  : 2026-07-31 14:22:55 : Line                                     -Unable to get Token Profile by ID: null.Required data is missing from command
Info   :                                                                -Exit code: 1
EOJ    : 2026-07-31 14:22:55 - Terminating

AMBA will output LTIF sorted by serial numbers in ascending order.  The last serial number in the AMBA output will be the last one before encountering the token with invalid data.

To find the problem token, run the Software Tokens report in the Security Console, focusing on these data fields:

Run the report and sort by token serial number to match the AMBA output.  Look at the first assigned token after the last token in the AMBA report.

This next token likely has data that is corrupt or invalid.

Unassign the token in question, then run the AMBA report again.  Verify if the total output matches the output of the Software Tokens report.  If so, the token can be reassigned and distributed to the user.