ADFS tweaks

[ptbrowne]

Goals

Polishing login via government ADFS. Each commit should be self explanatory.

• Added variables to Gitlab
• Removed old keycloak variables (must be done when PR is merged)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
visualization-tool	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 29, 2024 8:38am

[ptbrowne]

The build on Vercel is failing since Prisma schema sync tries to drop columns. I do not see those columns locally. Does it ring a bell @adintegra ?

⚠️ There might be data loss when applying the changes:
• You are about to drop the column created_at on the users table, which still contains 3 non-null values.
• You are about to drop the column updated_at on the users table, which still contains 3 non-null values.
Error: Use the --accept-data-loss flag to ignore the data loss warnings like yarn prisma db push --accept-data-loss
error Command failed with exit code 1.

[adintegra]

I think we could drop references to Keycloak altogether.

Alternatively, we could keep them (including what we had before in the Locally section below) and explain the use of Keycloak as an identity provider. Obviously more effort, but potentially more useful to other users of the project.

[ptbrowne]

Ah, I had forgotten this last mention. I removed it and pointed to the custom adfs provider. Thanks.

[adintegra]

LGTM – thanks! 🎉

[adintegra]

@ptbrowne just saw your comment on the dropping of columns. The columns were added in the branch I created (but not yet merged) yesterday. I suspect the migration must have been run from the branch and caused the schema drift.