Merged in SW-3476-use-separate-curity-client-for-service-tokens-for-partner-sas (pull request #2809)
feat(SW-3476): add support for using different curity clients when creating service tokens * fix(SW-3476): add support for using different curity clients when creating service tokens * remove log statement Approved-by: Hrishikesh Vaipurkar
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
NEXTAUTH_DEBUG="false"
|
||||
DEBUG_QUERIES="false"
|
||||
SEAMLESS_ENVIRONMENT_SUBDOMAIN="www"
|
||||
CURITY_CLIENT_SERVICE_SCOPES="profile, hotel, booking, package, availability"
|
||||
|
||||
SEAMLESS_LOGIN="https://${SEAMLESS_ENVIRONMENT_SUBDOMAIN}.scandichotels.{topleveldomain}/updatelogin"
|
||||
SEAMLESS_LOGOUT="https://${SEAMLESS_ENVIRONMENT_SUBDOMAIN}.scandichotels.{topleveldomain}/updatelogout?newweb=1"
|
||||
Reference in New Issue
Block a user