397 Commits (f9dfd024ed5f2ceb8959a295a43e070b9e1cbb6a)

Author	SHA1	Message	Date
Todd	fa39fe5b0f	Delete the base auth account when a concrete auth account is deleted (#2528)	4 years ago
Irena Rindos	4493dfd527	use prior and current worker auth keys (#2495) ... * use prior and current worker auth keys	4 years ago
Timothy Messier	a2ef14283b	fix(org): Address bug that prevented deleting an org (#2465) ... The schema changes introduced in 0.10.2 introduced a bug where an org could not be deleted if there was a session for an org scoped user. It would result in an error like: scope.(Service).deleteFromRepo: unable to delete scope: \ iam.(Repository).DeleteScope: failed for o_VkNy46KwfS: \ iam.(Repository).delete: db.DoTx: iam.(Repository).delete: \ db.Delete: insert or update on table "session" violates foreign key constraint "target_fkey": integrity violation: error #1003 A worker around would be to first delete all projects in the org, then finally delete the org. This fix adds a regression test to the sqltests and updates several constraints on the session table to be deferrable. Since the org delete is a single transaction, this allows all of the necessary resources to be deleted before attempting to enforce these constrains. See: https://www.postgresql.org/docs/current/sql-set-constraints.html Blame: 3a28ab614	4 years ago
Damian Debkowski	546c5dc5be	feat: static json credentials (#2423)	4 years ago
Irena Rindos	821d8317dc	address op state review feedback (#2453) ... * address op state review feedback	4 years ago
Jeff Mitchell	53b5e532d5	Remove deprecated methods/fields on targets (#2393)	4 years ago
Irena Rindos	fc0ead73e6	feat(workers): worker operational state (#2427) ... * feat(workers): worker operational state	4 years ago
Jeff Mitchell	9002930d65	Adapt shared lock skip logic to dbswap branch (#2437)	4 years ago
Hugo Vieira	bed6e1a0ff	feat(server): Reload database on SIGHUP ... If the database url is updated on Boundary's config and then a SIGHUP triggered, we now connect to the new database, ensure it's OK to use and use that one going forwards instead. This allows a controller to be deployed in a more dynamic infrastructure where, for example, database credentials could change, without having to restart the controller. In this case only a database url config change and a SIGHUP signal to all controllers would be required. This uses an atomic.Pointer to store wrapped DB objects. This allows atomically swapping to the new object. A timeout is introduced so that if the object is swapped after the existing one has been looked up it isn't immediately invalidated. The timeout is a maximum; a ticker once a second that looks at stats to determine how many database connections are still in use and then closes the driver as soon as none are in use. This could be done with mutexes to avoid checking stats in a loop, but that carries its own risk: if a write lock is attempted to be acquired while a query is holding a read lock, the write lock will block, and any subsequent read locks will also block since write locks take priority. As a result, if a query is long-running or timing out, all other queries in the system will become blocked. Our default user request timeout is 90 seconds and some jobs have no timeout at all, so this is not a purely theoretical concern, even if it's unlikely. Refs: #2435 Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>	4 years ago
Hugo Vieira	621f8a9ff2	fix(schema): Database connection not cleanly closed ... This commit introduces closing the Schema Manager's underlying driver connection. We were only releasing the shared lock but not actually cleaning up the db connection and relied on the fact that the process would exit to do that for us.	4 years ago
Irena Rindos	18dff62b7b	Merge BYOW GA branch to main (#2398) ... * feat(workers): Add ability to read and reinitialize cert authority (#2312) * feat(workers): Return Release Version on worker list and read (#2377) * feat(cli): Read and reinitialize worker certificate authority (#2387)	4 years ago
Timothy Messier	2fbdcf6ce0	feat(session): Use permissions for limiting list results ... The session repository can now be passed an optional set of permissions. The permissions are used to restrict results from the repository. Currently this only impacts the List method. This enabled the sessions service to use a single query to retrieve sessions and replaces the previous behavior where the session service would first request all sessions for a given set of scopes, evaluate the permissions, and then request sessions based on a set of session ids.	4 years ago
Louis Ruch	d7c4c648ec	bug(vault): Correctly handle credential stores with expired tokens (#2399) ... * bug(vault): Correctly handle credential stores with expired tokens Boundary makes use of a database view to perform CRUD operations on Vault credential stores and libraries. This view did not include credential stores with tokens that have expired in Vault, causing errors when attempting to perform any action against them.	4 years ago
Jeff Mitchell	01fb949d0b	Add controller-led worker auth flow (#2413) ... This adds an action to the API that allows pulling out an activation token that can be given to a worker in its config (directly or via env or file). The worker can pass this along with its normal request in place of its normal nonce and the server will automatically accept it. Co-authored-by: Irena Rindos <irenarindos@users.noreply.github.com>	4 years ago
Johan Brandhorst-Satzkorn	de2c40fa77	Fork pgtap-docker to support arm64 (#2411) ... * feat(sql): Fork pgtap to support arm64 This forks pgtap-docker and builds the image locally, and updates our references to use our forked image. * fixup! feat(sql): Fork pgtap to support arm64	4 years ago
Damian Debkowski	3f70644978	fix(db): update host_plugin_set to set project_id value (#2410)	4 years ago
Johan Brandhorst-Satzkorn	aef9073fa6	Upgrade to Go 1.19 (#2347)	4 years ago
Danielle	07a4082aa1	Add SQL Migration 05 From go-kms-wrapping (#2371) ... * adding sql migration 05 from go-kms-wrapping * rename file from 05 to 01 to match boundary standards * move key rewrap to folder 47	4 years ago
Johan Brandhorst-Satzkorn	d709b97e18	fix(schema): Panic with error rather than function (#2391)	4 years ago
Jim	b0bc6bd632	refactor: eliminate gorm references in favor of go-dbw (#2386)	4 years ago
Louis Ruch	929a385fdb	fix: move 'drop target_all_subtypes' after whx views	4 years ago
Damian Debkowski	27e9f775be	feat: add initial migration hook	4 years ago
Timothy Messier	79866a287f	feat(schema): Add support for migration hooks ... This adds the ability to define hooks that will run prior to a schema migration. The hooks should only be used when a migration would fail due to data being in an invalid state, likely due to a bug in the previous schema definition. For example if a column was missing a constraint, and a new migration is attempting to add the constraint, there might already be values that violate the new constraint. In such cases, we would want the user to make a decision to address the data, and need to provide them with details about what data is problematic in case they want to manually address the problem. To help the user, if there is a sane way to address the data, we should provide an option to automatically "repair" the data, allowing the migration to continue. However, this still should be an explicit opt-in from the user, and we need to clearly describe what the repair option would do to the user so they understand the consequences of opting in. To accomplish this each migration can be provided a hook that contains a CheckFunc, RepairFunc, and RepairDescription. These functions must operate at the point-in-time of the migration immediately preceding the current migration, as as such they should not use and domain packages or repositories, instead they should use direct sql with the sql library. The description is used to explain what the RepairFunc will do. Hooks should be defined in `internal/db/schema/migrations/oss/oss.go` and registered with the schema edition. See the example in `internal/db/schema/manager_example_test.go` for more details.	4 years ago
Michael Gaffney	1fa79e9aa1	test(db): Add tests for inserts into target_host_set	4 years ago
Michael Gaffney	0512ddb060	test(db): Add tests for inserts into target_credential_library	4 years ago
Damian Debkowski	c4aa9a0358	test(sql) add tests to validate project scope for target_static_credential	4 years ago
Johan Brandhorst-Satzkorn	222a935223	Update grpc-gateway dependency (#2311) ... * chore(deps): Update grpc-gateway dependency This fixes an issue which would allow an attacker to trigger a (recovered) panic in the gateway handler. * fix(server): Use cmp.Diff instead of assert.Equal Testify is not great at handling protobuf types, and was for some reason returning a diff here when in reality there is none. Switch to go-cmp for the comparison to remove the error.	4 years ago
Louis Ruch	d01f374490	bug(db): Fix credential purpose migration (#2351) ... * bug(db): Fix credential purpose migration	4 years ago
Michael Gaffney	a6d9c228aa	Merge branch 'mgaffney-greppable-sql'	4 years ago
Jim	7aa7deafa3	chore: update go-dbw dependencies (#2298) ... * chore: update go-dbw dependencies This update included an update of the upstream gorm dependency. In the latest update, gorm appears to have become more sensitive when a slice is passed into operations. The ptr to slice must now be a ptr to slice of ptrs. This change required an update to how boundary handles slices of PrincipalRole, which now must return a ptr to PrincipalRole. There were also some tests that needed to be updated because of this change. * fixup! chore: update go-dbw dependencies	4 years ago
Louis Ruch	7fafadd70b	db: Add credential_sha256 to session_credentials (#2339) ... * db: Add credential_sha256 to session_credentials	4 years ago
Michael Gaffney	ac6f14a37f	style(sql): make migrations more greppable	4 years ago
Jeff Mitchell	02dd28f587	Add support for SSH private key passphrases (#2331) ... This adds support for encrypted SSH keys via passphrase. Co-authored-by: Louis Ruch <louisruch@gmail.com> Co-authored-by: Michael Gaffney <mgaffney@users.noreply.github.com>	4 years ago
irenarindos	4908aba546	feat(vault): Add unimplemented worker filter support to OSS	4 years ago
Louis Ruch	a17e973712	feat(credentials): Refactor credential purposes (#2260) ... * feat(credentials): Refactor credential purposes * Application credentials have been refactored to Brokered credentials * Egress credentials have been refactored to Injected Application credentials Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>	4 years ago
Louis Ruch	ef5ac07f02	Add ssh_private_key support for Vault libraries and targets (#2263) ... * Add support for ssh_private_key credential type in Vault libraries * Add support for ssh_private_key credential type * Support jsonpointer for Vault library mapping overrides	4 years ago
Jeff Mitchell	011e2e7425	Add ssh private key type and add type to static store (#2262) ... Co-authored-by: Louis Ruch <louisruch@gmail.com>	4 years ago
Jim	3da78aa7e4	refactor (kms): Update dependency required a small refactor (#2253)	4 years ago
Jeff Malnick	1f66685864	feat: set default connection limit to unlimited (-1) instead of 1 (#2234) ... This avoids the confusion behavior of a session terminating as soon as a single connection using that session is closed.	4 years ago
Timothy Messier	fd5d15af27	feat(config): Add database config options for idle connection management (#2176) ... This adds two new config options for the `database` stanza: - `max_idle_connections` - `max_idle_time` These correspond to settings for the underlying `sql.DB` instance. They can be used to have finer control over the controller's database connection pool. For example this can be used to mitigate the high connection overhead when connecting to postgres by setting a high `max_idle_connections` and either setting `max_idle_time` to zero or to a high duration. Alternatively, if using a connection pool like pgpool-II or pgbouncer, `max_idle_connections` can be set to 0. See: https://pkg.go.dev/database/sql#DB.SetMaxIdleConns https://pkg.go.dev/database/sql#DB.SetConnMaxIdleTime https://www.pgpool.net/mediawiki/index.php/Main_Page https://www.pgbouncer.org/	4 years ago
Damian Debkowski	3e9c99c217	refactor(user_password) rename all references of user_password to username_password (#2232)	4 years ago
Jeff Mitchell	396edfca80	Add an extra cleanup task for sessions stuck in canceling state (#2229) ... * Add an extra cleanup task for sessions stuck in canceling state See the comment on the migrations file for details.	4 years ago
Louis Ruch	4cacd0a605	bug(scheduler): Fix controller id length check (#2226) ... * bug(scheduler): Fix controller id length check The job_run table has a foreign key to the server_controller private_id. While this column is called a prviate_id it does not implement the wt_private_id postgres domain type, and therefore does not have a minimum length of 10 characters.	4 years ago
Timothy Messier	f3c90df300	chore(db): Silence db logs by default for tests ... This removes a lot of log clutter from normal test execution with `go test -v`. There are a number of test that expect no results from the database or other error cases from the database. The previous default log level of dbw.Error would cause these cases to generate logs in the success case, creating noise in the test output. The new default for tests is dbw.Silent. This can be overriden in two ways. A test can be updated to pass in the db.WithTestLogLevel option, which allows for targeting specific tests to include additional output. This may make sense for tests that normally should not cause errors, but would report an error if it fails. Alternatively a new environment variable can be set, DEFAULT_TEST_LOG_LEVEL. This allows for adjusting the log level without changing any test file. The environment variable should be set to the string value of the log level, and is treated as case insensitive, ie: export DEFAULT_TEST_LOG_LEVEL="error"	4 years ago
Louis Ruch	9671daf6e0	Revert "refactor(user_passsword) change all references of user_password into username_password (#2189)" ... This reverts commit ab58b24142.	4 years ago
Damian Debkowski	ab58b24142	refactor(user_passsword) change all references of user_password into username_password (#2189) ... * (refactor) change all sql references of user_password to username_password * refactor(pkg) renamed pkg userpassword to usernamepassword * refactor(proto) updated protocol buffers to use UsernamePassword * refactor(code) updated references from UserPassword to UsernamePassword in golang files * refactor(test) updated unit tests to reference UsernamePassword changes * refactor(ddtest) updated references in dbtests to use UsernamePassword * chore(sql-test) fixed spelling issue * chore(sql) added and updated comments in migartion & tables. fixed indentations * chore(proto) updated comments to reflect username_password changes * refactor(tests) updated unit tests to replace user-password with username-password * refactor(cmd) updated cmd help text to use username * chore(tests) update test name & comments * fix(cmd) fixed cmd usage definition for credentials update * refactor(tests) removed out of scope changes * fix(sql) incremented sql migration id & updated migration comments	4 years ago
Jeff Mitchell	704d68848c	Merge remote-tracking branch 'origin/main' into llb-byow	4 years ago
Jeff Mitchell	b0480eb7b3	Move migrations to 32	4 years ago
Todd	beecbbb8a2	Upsert creates a new KMS and Updates PKI workers (#2187)	4 years ago
Irena Rindos	06d0f99536	bug(workersAPI): do not allow nonprintable or uppercase name or desc (#2186) ... * Send more info on KMS connect (#2182) * Update nodeenrollment to v0.1.0 * bug(workersAPI): do not allow nonprintable or uppercase name or desc * Put checks on create too * Apply printable check to description in DB * chore (worker): address PR feedback Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com> Co-authored-by: Jim <jlambert@hashicorp.com>	4 years ago