-
-
-
- Building blocks of the data model
- Basic concepts
- Classes
- Key fields
- Local lookup lists
- Fields and data types
- Defining the columns of a table
- Relations between classes
- Global lookup lists
- Filters
- Universal connected classes
- Deleting foreign records
- Class inheritance
- Storage of personal data on test and develop environment (scrambling)
-
- Resource files
- Velocity - How does it work?
- Quick Velocity Tutorial
- Debugging velocity scripts
- Velocity Command Reference
- Script Editor Tutorial
- Using velocity for calculations
- Using predefined forms in a html design
- Velocity forms
- Data field identifiers
- Macros and methods
- Velocity library
- Velocity: using the #macro command
- velocity and xml
- Using AJAX in your velocity scripts
-
-
- Argon2 password conversion
- Introduction to security
- Secure development
- Security certification
- Security Exam
- Field properties concerning security
- Developing user groups securely
- Security considerations for user interface
- Secure file organization
- Securely using the request
- Cross Site Scripting (XSS)
- Other options concerning secure development
- Security analysis
- Secure deployment
- Secure application management
- Scrambling of testdata
- Anonymization of personal data
- Using robots.txt
- Permission settings
- Security measures
- Data encryption
-
- Search Engine Optimization
- OTP
- User Interface migration guide
- User account management
- Instructies voor implementatie van visueel editen van nieuwsbrieven
- Login as another user
- Support
- More information about moving to User Interface Version 4.0
- Standaard page layout
- Sections moved to layout
- Aanpassingen in release 2024-7
- Media library
- Aanpassingen in release 2024-10
- Analytics and Matomo
- Registration forms
- How to change names of classes and fields?
- Responsible Disclosure Policy
- How to upload a blob in Velocity?
- Aanpassingen in release 2024-2
- Instances
- Componenten in onze technologie
- Google Analytics
- Street and City helper (postcodecheck)
- Responsible disclosure-beleid
- Postcode check service (straat en huisnummer) kosten
- Expressions
- Regular Expression Reference
-
Argon2 password conversion
Passwords are saved as hashes in the database. Argon2 is among the strongest hashing methods currently available, meaning it requires a great amount of computation power to brute force.
Converting existing passwords to use Argon2 hashing can be done through an action in the backstage of your application. To gain access to this action, contact Crossmarx.
Argon2 password hashing requires a 'pepper' file to be present in the application, and each password to be 'salted'. The action takes care of both.
Using the action, if there is no pepper file present yet, you will be prompted to create one.
If there is a pepper file present, you can start converting existing passwords to use Argon2. This process can be stopped and restarted at any point. Passwords that have been converted will use Argon2, those that have not been converted yet, will still use the previous hashing method.
This conversion may take a while (around 1 second per password) and may use up many resources. Take this into account when planning this conversion.
Note that once a pepper file has been created, new passwords will automatically be hashed with Argon2.
Currently the action is located in the backstage menu under 'Database -> Upgrade password security'.