Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

Configuring SQL Authentication

You must configure both Steel-Belted Radius Carrier and the SQL database to support SQL authentication. The configuration procedure must be tailored to the database that you use. However, all procedures must give the following results:

  • The required transport must be in place between SQL client software and the SQL server.
  • The SQL server must be configured via a plug-in to coordinate with SQL client software.
  • The Steel-Belted Radius Carrier server must be configured to communicate with the SQL client software to interact with the back-end SQL server to perform stored procedures or SQL queries.


The files in Table 48 establish settings for configuring SQL authentication in Steel-Belted Radius Carrier. For more information about these files, refer to the SBR Carrier Reference Guide.

Table 48: SQL Authentication Files

File Name



Configures settings for SQL authentication using Oracle.


Configures settings for SQL authentication using JDBC.

Using the SQL Authentication Configuration File

To configure SQL authentication, you must edit the authentication configuration files, radsql.aut (Solaris with Oracle) or radsqljdbc.aut (Solaris with JDBC), which are located in the same directory that contains the Steel-Belted Radius Carrier daemon. Most of these options may be left at their original settings; however, you must modify certain options to accommodate your own database.

After you complete your changes to the authentication configuration files and restart Steel-Belted Radius Carrier, the InitializationString value that you entered in the [Bootstrap] section of the configuration file appears in the Authentication Methods page. You can then enable, disable, or prioritize your SQL database like any other authentication method in the list.

Using Multiple SQL Authentication Methods

You can configure Steel-Belted Radius Carrier to authenticate users against more than one SQL database. Each database that you set up in this way becomes a separate selection in the Authentication Methods page.

To add an additional database, create a new configuration file with extension .aut in the same directory as radsql.aut (Solaris with Oracle) or radsqljdbc.aut (Solaris with JDBC). You can give this file any name you like, provided its extension is .aut. At startup, Steel-Belted Radius Carrier enumerates all .aut files to create its list of authentication methods.

When creating the new file, start by copying the original .aut file. Be sure to change its InitializationString entry to a unique authentication method name; otherwise, Steel-Belted Radius Carrier has no way of distinguishing between the different methods in the authentication methods list.

Modified: 2018-01-11