11 Commits (1dfff74da957a6264b53a3459101406f869edc2d)

Author	SHA1	Message	Date
Dan Cech	1dfff74da9	move database-specific code into dialects (#11884)	7 years ago
Marcus Efraimsson	ef3588c1f8	docker: mssql and mssql tests blocks with common build context	7 years ago
Marcus Efraimsson	57d46a706c	mssql datasource: additional data type tests	7 years ago
Leonard Gram	b60b6690ba	sql: removes locale from test to mirror prod.	7 years ago
Marcus Efraimsson	3d1c624c12	WIP: Protect against brute force (frequent) login attempts (#10031) ... * db: add login attempt migrations * db: add possibility to create login attempts * db: add possibility to retrieve login attempt count per username * auth: validation and update of login attempts for invalid credentials If login attempt count for user authenticating is 5 or more the last 5 minutes we temporarily block the user access to login * db: add possibility to delete expired login attempts * cleanup: Delete login attempts older than 10 minutes The cleanup job are running continuously and triggering each 10 minute * fix typo: rename consequent to consequent * auth: enable login attempt validation for ldap logins * auth: disable login attempts validation by configuration Setting is named DisableLoginAttemptsValidation and is false by default Config disable_login_attempts_validation is placed under security section #7616 * auth: don't run cleanup of login attempts if feature is disabled #7616 * auth: rename settings.go to ldap_settings.go * auth: refactor AuthenticateUser Extract grafana login, ldap login and login attemp validation together with their tests to separate files. Enables testing of many more aspects when authenticating a user. #7616 * auth: rename login attempt validation to brute force login protection Setting DisableLoginAttemptsValidation => DisableBruteForceLoginProtection Configuration disable_login_attempts_validation => disable_brute_force_login_protection #7616	7 years ago
linux chips	6f3a62d299	add _tests for mssql data source	8 years ago
mxlxm	c5400ffe76	mysql: use collation instead of charset (#9156) ... - use charset would issue additional 'SET NAMES <VALUE>' queries, set collation would be better. see: https://github.com/go-sql-driver/mysql#charset	8 years ago
Dan Cech	24d4e50343	utf8mb4 encoding (#7959) ... * use utf8mb4 character set for connections to mysql * use utf8mb4 character set for tables, shorten varchar fields used in unique indexes * migration type to update table character set * update table character sets * set charset for temp_user.status * gofmt	8 years ago
Torkel Ödegaard	b1f85dc8f1	Added expire option to dashboard snapshots, #1623	10 years ago
Torkel Ödegaard	afb847acc8	a lot of work on database schema and migration setup, postgres now works, every integration test passes for all database types, only token table left to do	10 years ago