Quentin
Quentin
Thank you all!
Well, it could be, but I don't want to create new users, but rather load one (or none) based on the SAML attributes. Is that compatible?
I've also considered this feature. But if I'm correct, it will inject SAML attributes in a User instance, which would have previously been loaded by the user provider. But what...
Isn't this also true for those lines? ```gitignore /yarn.lock /package-lock.json ``` Git-based deployment cannot work without those files 😉
I guess this is because of [Yarn's Zero-installs strategy](https://yarnpkg.com/features/caching#zero-installs).