From b26f2309f4f2361e99456882c85c9fa5c71f8255 Mon Sep 17 00:00:00 2001 From: Luke Taylor Date: Thu, 10 Mar 2011 13:41:17 +0000 Subject: [PATCH] Add paragraph to manual database appendix to clarify that the standard schema is completely optional if you aren't using JdbcDaoImpl. --- docs/manual/src/docbook/appendix-db-schema.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/manual/src/docbook/appendix-db-schema.xml b/docs/manual/src/docbook/appendix-db-schema.xml index c2dd64fbe1..b0a4bec76a 100644 --- a/docs/manual/src/docbook/appendix-db-schema.xml +++ b/docs/manual/src/docbook/appendix-db-schema.xml @@ -14,8 +14,8 @@ The standard JDBC implementation of the UserDetailsService (JdbcDaoImpl) requires tables to load the password, account status (enabled or disabled) and a list of - authorities (roles) for the user. - + authorities (roles) for the + user. create table users( username varchar_ignorecase(50) not null primary key, password varchar_ignorecase(50) not null, @@ -47,6 +47,12 @@ create table group_members ( group_id bigint not null, constraint fk_group_members_group foreign key(group_id) references groups(id)); + Remember that these tables are only required if you are using the provided JDBC + UserDetailsService implementation. If you write your + own or choose to implement AuthenticationProvider + without a UserDetailsService, then you have complete + freedom over how you store the data, as long as the interface contract is + satisfied.