53a3194d5c
* new saml branch * put saml info back in * put saml info back in * clean up code * validate saml config * validate schema * Add saml auth flow tests * use RelayState for redirects * Update tests for RelayState * Fix linting * remove validateMeta as samlify does it already * Fix linting * change catch on login * Update api/src/auth/drivers/saml.ts Co-authored-by: Aiden Foxx <aiden.foxx.mail@gmail.com> * remove login since not needed here * clear cookie if set on logout * empty login method * invalidate logout in db * if relayState and login failed, redirect back with a reason * Cleanup linter warnings * Remove range from packages * Opinions opinions opinions opinions Just a couple personal opinion cleanup pieces Co-authored-by: ian <licitdev@gmail.com> Co-authored-by: Aiden Foxx <aiden.foxx.mail@gmail.com> Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
Blackbox tests
Setup
Make sure the containers for the databases are running by running docker compose up -d in this folder.
Running tests locally
Run npm run test:blackbox to run the blackbox tests for every supported database vendor.
Testing a specific database
Provide a csv of database drivers in the TEST_DB environment variable to test specific databases:
TEST_DB=cockroachdb npm run test:blackbox
Using an existing Directus instance
The test suite will spin up a fresh copy of the Directus API from the current build. To use an already running copy of
Directus, set the TEST_LOCAL flag:
TEST_DB=cockroachdb TEST_LOCAL=true npm run test:blackbox
This will use localhost:8055 as the URL for every test. Note: make sure to connect your local Directus database
instance to the test database container found in docker-compose in this folder.
Watching for (test) changes
Use npm run test:blackbox:watch to enable Jest's --watch mode, especially useful in combination with the flags
above.
This does not watch changes to Directus; it only watches changes to the tests.