challenger-sms.conf.j2 (1382B)
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-sms/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-sms 16 17 # Name of a file with the message to send with the challenge. 18 MESSAGE_TEMPLATE_FILE = /etc/challenger/sms-message-template.txt 19 20 # Publicly visible base URL of the challenger. 21 # BASE_URL = https://example.com/ 22 BASE_URL = https://sms.challenger.{{ domain_name }}/ 23 24 # What address type are we validating? (phone, email, address, etc.) 25 # A template of the form 'enter-$ADDRESS_TYPE-form' must 26 # exist and the field names must be supported by the 27 # AUTH_COMMAND. 28 ADDRESS_TYPE = phone 29 30 # Hint to show on the address format. 31 ADDRESS_HINT = {{ EXCHANGE_AML_PROGRAM_TOPS_SMS_EXAMPLE }} 32 33 # Limit acceptable phone numbers. 34 ADDRESS_RESTRICTIONS = {"CONTACT_PHONE":{"hint":"{{ EXCHANGE_AML_PROGRAM_TOPS_SMS_HINT }}","regex":"{{ EXCHANGE_AML_PROGRAM_TOPS_SMS_REGEX }}"}} 35 36 37 [challengerdb-postgres] 38 # The connection string the plugin has to use for connecting to the database 39 CONFIG = postgres:///challenger-sms