1.0

Table Of Contents
The following sqlfire.properties entries show a SQLFire member that is congured to use SQLFire
built-in authentication:
sqlfire.auth-provider=BUILTIN
mcast-port=0
The mcast-port=0 entry indicates that multicast is not used in the SQLFire distributed system. Valid locator
properties would need to be supplied when starting the SQLFire server, as well as the credentials for a SQLFire
user as described in Creating Users for BUILTIN Authentication on page 231.
Creating Users for BUILTIN Authentication
The SQLFire BUILTIN authentication provider is suitable for development and testing only. When using this
security mechanism, the SQLFire system maintains the repository of username and password information.
BUILTIN User Accounts
The BUILTIN provider supports two different types of user account:
System user accounts are visible to all members of the SQLFire system, and have privileges to join members
to the cluster and shut down cluster members. The list of valid system users is established using system properties
when you boot a SQLFire server or locator. You should use only a few system-level users in a SQLFire
deployment (for example, one system user for a standalone locator and one for SQLFire servers).
You create user names and passwords for system users by specifying them with the
sqlfire.user.<UserName>=<password> property in the sqlfire.properties le. See Create
System Users on page 231.
Distributed system user accounts are used to establish connections to a SQLFire cluster and to protect database
resources using SQL authorization. You dene distributed system user credentials by connecting to a running
SQLFire system and executing a built-in procedure. Privileges on individual database resources are then granted
using SQL commands. See Create Distributed System Users on page 232.
Note: The SQLFire built-in authentication mechanism is suitable only for development and testing
purposes. Production systems should use LDAP or a user-dened class for authentication. Production
systems should also use SSL/TLS to protect network connections.
Create System Users
System users are established at boot time, and have privileges to join and start SQLFire servers and locators.
Procedure
1. Create a system user for SQLFire by specifying user name=password at boot time using the
sqlfire.user.UserName system property.
SQLFire user names are SQL92 identiers, and are case-sensitive for user authentication. Delimited identiers
are allowed.
For example, the following property denes a username of "FRed" with the password "java":
sqlfire.user."FRed"=java
2.
Include the property denitions for system users in the sqlfire.properties le for each SQLFire
server and standalone locator.
For example, this listing shows a sqlfire.properties le the denes a "locatoradmin" and
"serveradmin" system user:
sqlfire.auth-provider=BUILTIN
mcast-port=0
sqlfire.user.locatoradmin=locatorpassword
sqlfire.user.serveradmin=serverpassword
231
Configuring Authentication and Authorization