challenger-sms.conf.j2 (1540B)
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 {% if devtesting_mock_mfa | bool %} 16 AUTH_COMMAND = mock-mfa-sms 17 {% else %} 18 AUTH_COMMAND = challenger-send-sms 19 {% endif %} 20 21 # How long may an individual validation process take? 22 VALIDATION_DURATION = 7d 23 24 # Name of a file with the message to send with the challenge. 25 MESSAGE_TEMPLATE_FILE = /etc/challenger/sms-message-template.txt 26 27 # Publicly visible base URL of the challenger. 28 # BASE_URL = https://example.com/ 29 BASE_URL = https://sms.challenger.{{ domain_name }}/ 30 31 # What address type are we validating? (phone, email, address, etc.) 32 # A template of the form 'enter-$ADDRESS_TYPE-form' must 33 # exist and the field names must be supported by the 34 # AUTH_COMMAND. 35 ADDRESS_TYPE = phone 36 37 # Hint to show on the address format. 38 ADDRESS_HINT = {{ exchange_aml_program_tops_sms_example }} 39 40 # Limit acceptable phone numbers. 41 ADDRESS_RESTRICTIONS = {"CONTACT_PHONE":{"hint":"{{ exchange_aml_program_tops_sms_hint }}","regex":"{{ exchange_aml_program_tops_sms_regex }}"}} 42 43 44 [challengerdb-postgres] 45 # The connection string the plugin has to use for connecting to the database 46 CONFIG = postgres:///challenger-sms