Player Databases: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
For player specific passwords and public keys authentication a password file must be used as these require that the name of the players are fixed so that they can be matched to the specific password or public key. When starting the server you can specify that a password file is used. | For player specific passwords and public keys authentication a password file must be used as these require that the name of the players are fixed so that they can be matched to the specific password or public key. When starting the server you can specify that a password file is used. | ||
[[File:start-server-dialog-78032996b316cefe0aafca1c1d71ac9a.png| | [[File:start-server-dialog-78032996b316cefe0aafca1c1d71ac9a.png|left|Start Server with Player Database]] | ||
Revision as of 03:53, 22 April 2023
Player Databases
Authentication types
Prior to version 1.10 MapTool only supported a single method of authentication which is role based authentication. Each Role (GM and Player) has a password and any client that connects and authenticates with either of these passwords gets that role. There is no restriction player names other than everyone has to have a unique name.
In MapTool 1.10 or later there are three authentication methods.
- Role based
- Player specific passwords
- Public Key
Using Player Specific Authentication
For player specific passwords and public keys authentication a password file must be used as these require that the name of the players are fixed so that they can be matched to the specific password or public key. When starting the server you can specify that a password file is used.
