* fix: findLang only returns acceptable languages
* fix: fallback to use header x-lang if we haven't setLang yet
* fix: languageSchema, allow uppercase
Approved-by: Linus Flood
Fix: Use session.token.access_token if session exists in booking confirmation, else use serviceToken
* Fix: Added service token to safeProtectedProcedure
* fix: use of safeProtectedServiceProcedure
Approved-by: Michael Zetterberg
First steps towards the SAS partnership
* otp flow now pretends to do the linking
* Update LinkAccountForm header
* Update redirect times
* Clean up comments
* Set maxAge on sas cookies
* make all SAS routes protected
* Merge remote-tracking branch 'refs/remotes/origin/feature/sas-login' into feature/sas-login
* Require auth for sas link flow
* Fix resend otp
* Add error support to OneTimePasswordForm
* Add Sentry to SAS error boundary
* Move SAS_REQUEST_OTP_STATE_STORAGE_COOKIE_NAME
* Add missing translations
* Merge branch 'master' of bitbucket.org:scandic-swap/web into feature/sas-login
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* Add TooManyCodesError component
* Refactor GenericError to support new errors
* Add FailedAttemptsError
* remove removed component <VWOScript/>
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* remove local cookie-bot reference
* Fix sas campaign logo scaling
* feature toggle the SAS stuff
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* fix: use env vars for SAS endpoints
Approved-by: Linus Flood
- Do not throw in onError callback for server client. This lets the originating error bubble to Next.js.
- Do not log errors inside the service token procedure, server client onError callback will log all procedure errors.
- Log errors for fetching service token failure.