1.0

Table Of Contents
Chapter 42
Configuring Authentication and
Authorization
You secure a SQLFire deployment by conguring user authentication and SQL authorization, and enabling encryption
between members using SSL/TLS.
Note: Many topics in this chapter were adapted from the Apache Derby documentation source les, and are
subject to the Apache license:
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
Configuring User Authentication
When you enable user authentication, a valid username and password are required in order to start up a new
SQLFire member in the distributed system; join an existing distributed system; and connect to a running SQLFire
distributed system. SQLFire veries the name and password against a repository of users that is dened for the
system. Authentication is not enabled by default.
SQLFire authenticates users credentials against a repository of users that you specify. SQLFire provides a built-in
repository, or you can congure SQLFire to use an LDAP directory service or a custom authentication service
that you create.
Note: The SQLFire built-in authentication mechanism is suitable only for development and testing
purposes. Production systems should use an LDAP repository or custom directory service, and should
secure network connections using SSL/TLS.
229