16. Frequently Asked Questions

• 16.1. Customization
  • 16.1.1. Templates
    • 16.1.1.1. Translating templates
  • 16.1.2. Themes
    • 16.1.2.1. Providing your own stylesheet in the config file
    • 16.1.2.2. Use web server rewrite modules
    • 16.1.2.3. Use web server substitute module
  • 16.1.3. Logo
  • 16.1.4. Page title
  • 16.1.5. Menu
  • 16.1.6. Headers and Footers
  • 16.1.7. Tokenwizard
  • 16.1.8. Token customization
  • 16.1.9. New token classes
  • 16.1.10. Custom Web UI
• 16.2. How can I create users in the privacyIDEA Web UI?
• 16.3. So what’s the thing with all the admins?
• 16.4. What are possible rollout strategies?
  • 16.4.1. Autoenrollment
  • 16.4.2. Registration Code
  • 16.4.3. Automatic initial synchronization
• 16.5. How can I translate to my language?
• 16.6. What are possible migration strategies?
  • 16.6.1. RADIUS token migration strategy
  • 16.6.2. RADIUS PASSTHRU policy migration strategy
• 16.7. Setup translation
• 16.8. How can I setup HA (High Availability) with privacyIDEA?
  • 16.8.1. HA setups
    • 16.8.1.1. Using one central DBMS
    • 16.8.1.2. Using MySQL master-master-replication
• 16.9. MySQL database connect string
  • 16.9.1. MySQL-python
    • 16.9.1.1. Installation
  • 16.9.2. PyMySQL
    • 16.9.2.1. Installation
• 16.10. Are there shortcuts to use the Web UI?
• 16.11. How to copy a resolver definition?
• 16.12. Cryptographic considerations of privacyIDEA
  • 16.12.1. Encryption keys
  • 16.12.2. Token Hash Algorithms
  • 16.12.3. PIN Hashing
  • 16.12.4. Administrator Passwords
  • 16.12.5. Audit Signing
• 16.13. Policies
  • 16.13.1. How to disable policies?
  • 16.13.2. How do policies work anyway?
    • 16.13.2.1. How is this technically achieved?
• 16.14. Performance considerations
  • 16.14.1. Processes
  • 16.14.2. Config caching
  • 16.14.3. Logging
  • 16.14.4. Response
  • 16.14.5. Clean configuration
• 16.15. What happens in the tokenview?
• 16.16. How to mitigate brute force and lock tokens