10.11.1 breaks our SSO about directus

[keesvanbemmel]

So yeah, issue is resurfacing and I think I know where the problem lies:

After migrations we apply our own schema. When applying this schema the schema diff tells us that it will remove next_token from directus_sessions.

Now I know in the past, that these directus fields should be excluded from the diff alltogether? So definitely seems like a bug

[paescuj]

Did you run the migration ¹ when updating to 10.11.1?

Footnotes

1. https://docs.directus.io/self-hosted/upgrades-migrations.html#upgrading-updating-a-project ↩

[keesvanbemmel]

Yes I did, happens through our CICD pipeline. This is the migration that got logged:

[keesvanbemmel]

Ok, something weird happened. I looked at the migrations table and the Add Session Window was there. However the directus_sessions table didn't have a next_token column.

Reran the migration and not it works. No further action needed. Strange though.

[paescuj]

Good catch! Thanks @keesvanbemmel!