Database settings
If you already have an accounts database on your site
or in your app, you will most probably have the necessary fields
(telephone number, PIN or password field and - optionally -
e-mail address) that topID uses to deliver its service.
In theory, de database schema that contains your accounts, could
use one to four linked tables. If more than one table is used,
you will have to fill in the table and field names of the JOIN
key in order for topID to be able to work with your accounts
database.
You will have to fill in the fields that hold your database
credentials for topID to be able to gain access to your database
and provide its service. All database
credentials will be hashed before sending them to topID. We advice you to create a special
database account for topID to use, with only the necessary rights
activated (read/write on the tables that hold the key fields
MSISDN, PIN/password and optionally e-mail address; since topID
will use your existing accounts management page, we don't need
add/delete rights).
On the other hand, you might not have a need for, or not come around
to using an
accounts structure for your site or app. In this case, you could
use the accounts structure of topID. topID needs accounts for its
service anyway, so if your site or app doesn't need more than
getting users to authenticate, it's most practical to use topID's
accounts database. You don't have to provide database credentials
and specifics to start using the service of topID.
Host *
In this field you need to enter the name of
the database host of the database that holds your accounts.
Name *
In this field you need to enter the name of
the database that holds your accounts.
User *
In this field you need to enter the user
name of the database account that topID may use. We advice
you to create a dedicated database account for this with only
read/write rights on the table(s) that hold(s) the critical
fields MSISDN and PIN/password, and optionally e-mail address.
Password *
In this field you need to enter the password of
the database account that topID may use.
First JOIN key
If your database schema uses more than one
table to hold the needed data of MSISDN, PIN/password and
optionally e-mail address, at least two table will have to be
linked to retrieve or store the necessary information. In
these two fields you can enter the table name and field name of
the key join field by which the first two tables are joined
together.
Second JOIN key
If you need to fill in a second JOIN key,
you use at least three linked tables to hold the needed data of MSISDN, PIN/password and
optionally e-mail address. In
these two fields you can enter the table name and field name of
the key join field by which the second pair of tables are joined
together.
Third JOIN key
If you need to fill in a third JOIN key,
you use four linked tables to hold the needed data of MSISDN,
PIN/password and
optionally e-mail address. In
these two fields you can enter the table name and field name of
the key join field by which the third pair of tables are joined
together.
MSISDN *
This field holds the account's telephone
number. This is the number that topID compares to the number
that is used by the end-user. MSISDN is an acronym with
multiple explanations, the most common one being 'Mobile
Station International Subscriber Directory Number'. It
formats a phone number in an international format, including
the country calling code, the national destination code and
the subscriber number. It typically looks something like
'+31612345689' or '+31351234567'. We advice you to change the
validation of
the
phone number field in your database to store the numbers in
MSISDN format, if you are not doing so already. One of the
benefits will be that it doesn't matter from where in the
world you would dial such a number, you will always be
correctly connected. You need to fill in the table name and
field name of the field where your database stores the phone
numbers in.
PIN or password *
If you choose to use the existing password
field for the second factor of the authentication, you
probably will have some trouble. Presumably your password is
stored in the database hashed. This means that you cannot
decrypt it to a readable form. Your site or app will use its
own hashing algorithm and key-pare, which are not compatible to
topID's. So, it will be difficult, if not impossible, to use
your existing passwords with topID, unless they are stored in
readable form. It might be a better idea to add a field to the
table to store a PIN (topID stores PIN's hashed too) as
second factor. Either way, here you need to enter the name of
the table and of the field that your database uses to store
this information.
E-mail
If you will use this field is optional and
depends on the way you will allow your end users to reset
their PIN or password. topID supports resetting the PIN or
password using e-mail, SIM message or your help desk. If you
choose to support resetting the PIN or password using e-mail,
you should fill in the table and field name of the field your
database uses to store the end users's e-mail address.
