RSA Authentication Manager 8.1 Authentication Bit Flag Report (Licensing)
Originally Published: 2017-09-06
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1 SP1 or later
Issue
Resolution
A shell script named abf-report.sh, along with abfcompare.csv are attached to this knowledge article. These files are used to generate a report showing the authentication bit flag data and the report performs its own Users with Assigned Authenticators count using this authentication bit flag data.
Installation and Usage
- Download the attached abf-report.sh and abfcompare.csv files. Place them into /tmp on the RSA Authentication Manager primary instance using a secure FTP client (e.g. WinSCP).
- Launch an SSH client, such as PuTTY.
- Login to the primary RSA Authentication Manager server as rsaadmin and enter the operating system password.
Note that during Quick Setup another user name may have been selected. Use that user name to login.
- Change the permissions of abf-report.sh, so it can be executed at the command line:
chmod 775 /tmp/abf-report.sh
- Change the privileges of rsaadmin with the following command
sudo su -
Should the administrator forget to change the privileges and run the report from the /tmp folder, the following is seen:
rsaadmin@am84p:/tmp> ./abf-report.sh <enter Operations Console administrator password>
You must be the root user to use this program; exiting...
- Navigate to /tmp:
cd /tmp
- Run a report from /tmp on the RSA Authentication Manager primary instance with the command ./abf-report.sh [ocadmin] [password]. For example:
am84p:/tmp # ./abf-report.sh ocadmin p4ssw0rd!
Checking OC credentials..
OC credentials validated..
- collecting Authentication Bit Flag (ABF) data.. done!
Authentication Bit Flag Report - filename: /tmp/abf_report_202004061349.log
1 0000000
5 0001000
3 0100000
1 0100010
9 0101000
1 0101100
1 100
3 1000000
1 1000000000
7 1001000
1 1001100
..completed.
Counting the number of users with authenticators..
0100010,extuser,ODA
1001000,intuser,STorFP
1001000,intuser,STorFP
1001000,intuser,STorFP
0001000,intuser,STorFP
1001000,intuser,STorFP
0001000,intuser,STorFP
0101000,extuser,STorFP
0101000,extuser,STorFP
0101000,extuser,STorFP
0101000,extuser,STorFP
1001000,intuser,STorFP
0101100,extuser,STorFP&SecQ
1001000,intuser,STorFP
0101000,extuser,STorFP
0001000,intuser,STorFP
1001000,intuser,STorFP
1001100,intuser,STorFP&SecQ
0001000,intuser,STorFP
0001000,intuser,STorFP
0101000,extuser,STorFP
0101000,extuser,STorFP
0101000,extuser,STorFP
0101000,extuser,STorFP
Total count: 24
- cleaning up ABF data files.. done!
- cleaning up temporary file.. done!
Press any key to continue...
The reference to the Authentication Bit Flag Report lists the file to review. In the output above the file is /tmp/abf_report_202004061349.log. An example of the output is shown here:
rsaadmin@am84p:/tmp> cat /tmp/abf_report_202004061358.log
Authentication Bit Flag Report - filename: /tmp/abf_report_202004061358.log
1 0000000
5 0001000
3 0100000
1 0100010
9 0101000
1 0101100
1 100
3 1000000
1 1000000000
7 1001000
1 1001100
..completed.
Counting the number of users with authenticators: 24
There is additional information displayed on the screen that does not go into the report. Should you wish to keep this information, copy and paste the data into a text editor, such as Notepad++.If you forget to enter the Operations Console credentials, you will be prompted to enter them; for example:
am84p:/tmp # ./abf-report.sh Checking OC credentails....missing OC credentials! Please enter OC Administrator username: <enter Operations Console administrator name> Please enter OC Administrator password: <enter Operations Console administrator password> OC credentials validated..The rest of the report is then displayed.
Notes
Legend for the on screen report
| HT | Hardware Token |
| STorFP | Software Token or Fixed Passcode |
| SecQ | Security Questions |
| ODA | On-Demand Authentication |
| RBA | Risk Based Authentication |
| 100 | Internal user named @PROXYUSER@ |
| 1000000000 | Internal user named trustedapp |
Attachments
If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).
Related Articles
Generate a report of licensing limits for RSA Authentication Manager 8.3 and higher Number of Views Licensing for Oracle Automatic Workload Repository (AWR) with RSA Governance & Lifecycle Number of Views SA "All in One" Appliance licensing error: "smcBroker feature is not available for service with Computer id XXXXX" Number of Views error_log reports (ERROR) WsalWriteClient() failed with return code = [103] Number of Views User Picker ignores Include Terminated User flag in Via Lifecycle and Governance Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
