Database Table Structure

Web Flow requires a database to store data. It is tested with MySQL and Oracle, but should be easily adapted to any other SQL database which supports JDBC.

Web Flow can coexist with PowerAuth in the same database schema or it can use a different database schema.

Database Scripts

MySQL

• create_schema.sql - DDL script for creating the database schema
• initial_data.sql - script with initial data
• drop_schema.sql - drop schema script

Oracle

• create_schema.sql - DDL script for creating the database schema
• initial_data.sql - script with initial data
• drop_schema.sql - drop schema script

Database Tables

Database Tables for the OAuth 2.0 protocol

• oauth_client_details - the table stores details about OAuth2 client applications. Every Web Flow client application should have a record in this table. See JdbcClientDetailsService.java.

• oauth_client_token - the table stores OAuth2 tokens for retrieval by client applications. See JdbcClientTokenServices.java.

• oauth_access_token - the table stores OAuth2 access tokens. See JdbcTokenStore.java.

• oauth_refresh_token - the table stores OAuth2 refresh tokens. See JdbcTokenStore.java.

• oauth_code - the table oauth_code stores data for the OAuth2 authorization code grant. See JdbcAuthorizationCodeServices.java.

Database Tables for the Next Step Server

• ns_auth_method - the table stores configuration of authentication methods. Data in this table needs to be loaded before Web Flow is started.

• ns_user_prefs - the table stores user preferences. Status of authentication methods is stored in this table per user (methods can be enabled or disabled).

• ns_operation - the table stores details of Web Flow operations. Only the last status is stored in this table, changes of operations are stored in table ns_operation_history.

• ns_operation_config - the table stores configuration of Web Flow operations including configuration of mobile templates.

• ns_operation_history - the table stores all changes of operations.

• ns_step_definition - the table stores definitions of authentication/authorization steps. Data in this table needs to be loaded before Web Flow is started.

• ns_operation_afs - the table stores responses from AFS for operations.

Database Tables for the Data Adapter

• da_sms_authorization - the table stores data for SMS OTP authorization.

• da_user_credentials - the table stores user credentials.

Database Tables for the Web Flow Server

• wf_operation_session - the table stores mapping of operations to HTTP sessions.

• wf_afs_config - the table stores configuration of anti-fraud system integration.

Database Tables for the Third Party Provider

• tpp_consent - the table stores definitions of consents.

• tpp_user_consent - the table stores consents given by the user.

• tpp_user_consent_history - the table stores changes of consents given by the user.

• tpp_detail - the table stores information about third parties.

• tpp_app_detail - the table store information about third party applications.