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



Database Tables

Database Tables for the OAuth 2.0 protocol

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.

Database Tables for the Data Adapter

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

Database Tables for the Web Flow Server

  • wf_operation_session - the table stores mapping of operations to HTTP sessions.
Last updated on Jan 23, 2019 (19:02) Edit on Github Send Feedback


PowerAuth Web Flow