challenger-email.conf.j2 (1504B)
1 # General settings for the backend. 2 [challenger] 3 4 # Use TCP or UNIX domain sockets? 5 SERVE = UNIX 6 7 # Which unix domain path should we bind to? Only used if "SERVE" is 'unix'. 8 UNIXPATH = /run/challenger-email/challenger-http.sock 9 10 # What should be the file access permissions (see chmod) for "UNIXPATH"? 11 UNIXPATH_MODE = 666 12 13 # Which external command should be used to transmit challenges? 14 # Example commands are challenger-send-{sms,email,post} 15 AUTH_COMMAND = /usr/bin/challenger-send-email 16 17 # How long is an individual validation request valid? 18 VALIDATION_DURATION = 7d 19 20 # How long is an validation valid? 21 VALIDATION_EXPIRATION = 3650d 22 23 # Name of a file with the message to send with the challenge. 24 MESSAGE_TEMPLATE_FILE = /etc/challenger/email-message-template.txt 25 26 # Publicly visible base URL of the challenger. 27 # BASE_URL = https://example.com/ 28 BASE_URL = https://email.challenger.{{ domain_name }}/ 29 30 # What address type are we validating? (phone, email, address, etc.) 31 # A template of the form 'enter-$ADDRESS_TYPE-form' must 32 # exist and the field names must be supported by the 33 # AUTH_COMMAND. 34 # 35 ADDRESS_TYPE = email 36 37 # Hint to show on the address format. 38 ADDRESS_HINT = "user@example.com" 39 40 # What addresses are allowed. 41 ADDRESS_RESTRICTIONS = {"CONTACT_EMAIL":{"hint":"valid e-mail address required","regex":"^[a-zA-Z0-9_.+-]+@[a-zA-Z0-9-]+.[a-zA-Z0-9-.]+$"}} 42 43 [challengerdb-postgres] 44 #The connection string the plugin has to use for connecting to the database 45 CONFIG = postgres:///challenger-email