error:
va-sdk:INFO: set __webpack_public_path__ from "" to "https://cdn.developer.sas.com/packages/va-report-components/latest/dist/umd/" using "https://cdn.developer.sas.com/packages/va-report-components/latest/dist/umd/va-report-components.js"
va-report-components.js:18 LTJS load: WASM load time: 290.1000000014901 ms
ltjsRuntime.js:56 LTJS: getFormatLocale en-GB
ltjsRuntime.js:57 LTJS: getLocale en-GB
ltjsRuntime.js:96 *******************************
ltjsRuntime.js:97 LTJS PLATFORM INITIALIZATION SUCCESS
ltjsRuntime.js:98 *******************************
authorizeImpl.ts:113 GET https://sasviya-measureme.saasnow.com/SASLogon/oauth/authorize?client_id=sas.identities&redirect_uri... 401
O @ authorizeImpl.ts:113
authorize @ authorizeImpl.ts:450
(anonymous) @ authorization.ts:69
U @ Logon.tsx:102
authorizeImpl.ts:451 GET https://sasviya-measureme.saasnow.com/SASLogon/oauth/authorize?client_id=sas.reports&redirect_uri=/r... 401
authorize @ authorizeImpl.ts:451
(anonymous) @ authorization.ts:69
U @ Logon.tsx:102
authorizeImpl.ts:121 Uncaught (in promise) Error: [authorization] Unable to update user, invalid identities response
at O (authorizeImpl.ts:121:11)
at async Promise.all (:63343/webapps/index 0)
how to set grant on raport? what is the possible rease for this i have done all teh document requiments
I think this has bearing from your log:
Error: [authorization] Unable to update user, invalid identities response at O (authorizeImpl.ts:121:11)
Which would tell me that something was not received that the connection expected. What, can't say.
but I didn't make a separate setting in sas, this comes from the log:
{"version":1,"timeStamp":"2023-08-21T12:46:59.047Z","level":"warn","source":"sas-logon-app","message":"Handling error: RedirectMismatchException, Redirect URI mismatch.","properties":{"logger":"org.cloudfoundry.identity.uaa.oauth.token.UaaTokenEndpoint","thread":"https-jsse-nio-0.0.0.0-8080-exec-2","traceId":"0a4851dc00956ca6","spanId":"0a4851dc00956ca6","spanExportable":"true"}} {"version":1,"timeStamp":"2023-08-21T12:46:59.063Z","level":"warn","source":"sas-logon-app","message":"Handling error: InvalidGrantException, Invalid authorization code: 2RvH2QJhux","properties":{"logger":"org.cloudfoundry.identity.uaa.oauth.token.UaaTokenEndpoint","thread":"https-jsse-nio-0.0.0.0-8080-exec-29","traceId":"8132aeebd5daf4ac","spanId":"8132aeebd5daf4ac","spanExportable":"true"}} {"version":1,"timeStamp":"2023-08-21T12:46:59.193Z","level":"warn","source":"sas-logon-app","message":"Handling error: InvalidGrantException, Invalid authorization code: 2RvH2QJhux","properties":{"logger":"org.cloudfoundry.identity.uaa.oauth.token.UaaTokenEndpoint","thread":"https-jsse-nio-0.0.0.0-8080-exec-25","traceId":"674d5c1fe236cd38","spanId":"674d5c1fe236cd38","spanExportable":"true"}} {"version":1,"timeStamp":"2023-08-21T16:55:33.22Z","level":"info","source":"sas-logon-app","message":"A cookie header was received [SameSite=Lax, JSESSIONID=4023f724-b75d-479d-964f-0693237c3779;] that contained an invalid cookie. That cookie will be ignored.\n Note: further occurrences of this error will be logged at DEBUG level.","properties":{"logger":"org.apache.tomcat.util.http.parser.Cookie","thread":"https-jsse-nio-0.0.0.0-8080-exec-51"}} {"version":1,"timeStamp":"2023-08-21T19:04:26.204Z","level":"warn","source":"sas-logon-app","message":"Handling error: RedirectMismatchException, Redirect URI mismatch.","properties":{"logger":"org.cloudfoundry.identity.uaa.oauth.token.UaaTokenEndpoint","thread":"https-jsse-nio-0.0.0.0-8080-exec-41","traceId":"3df6bf5a06369980","spanId":"3df6bf5a06369980","spanExportable":"true"}} {"version":1,"timeStamp":"2023-08-21T19:04:26.314Z","level":"warn","source":"sas-logon-app","message":"Handling error: InvalidGrantException, Invalid authorization code: bkCBHr95U8","properties":{"logger":"org.cloudfoundry.identity.uaa.oauth.token.UaaTokenEndpoint","thread":"https-jsse-nio-0.0.0.0-8080-exec-2","traceId":"98f25b3ea4c786da","spanId":"98f25b3ea4c786da","spanExportable":"true"}}
which direction should I go? i have followed this documentation https://communities.sas.com/t5/SAS-Communities-Library/Embedded-Insights-with-SAS-Visual-Analytics-S...
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.