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:
@@ -15,7 +15,7 @@ export async function getServiceToken() {
|
||||
const tracer = trace.getTracer("getServiceToken")
|
||||
|
||||
return await tracer.startActiveSpan("getServiceToken", async () => {
|
||||
const scopes = ["profile", "hotel", "booking", "package", "availability"]
|
||||
const scopes = env.CURITY_CLIENT_SERVICE_SCOPES
|
||||
|
||||
const cacheKey = getServiceTokenCacheKey(scopes)
|
||||
const cacheClient = await getCacheClient()
|
||||
|
||||
Reference in New Issue
Block a user