Getting message “Error in importing encoded SAS KEY value for ADB2CTOKEN” when starting the report “ZADF_DEMO_AZURE_GRAPH” – different than issues #97 and #48? about abap-sdk-for-azure

[leofrederiksen]

Hi Henning
The transfer of data to Event Hub is working without errors for us as long as we dont have parallel processes trying to read the SAS Key/Token.
We are using SLT SDK to move all table changes to Azure, and SLT has to use parallel processes, otherwise the system will not be able to keep up with all the changes made in SAP.
The SLT feature is actually part of S4 Core systems (installed by default).
We are still trying to understand the error we have with the Azure SDK as it seems to be a design flaw.

[vikasbansal2022]

Hi @iloveabap
The index table ZADF_CON_INDX is filled with encrypted key when maintaining the entry in table ZADF_CONFIG via TMG events based on interface ID.

Please let us know if you still facing this problem. we can have a look at it.

Regards,
Vikas

[leofrederiksen]

Hi Vikas
I notived you closed this one, and I am unsure how to proceed. We have been searching for other tools to get data from SAP into Azure, but I really like this interface.
Anyway possible to have a view at it together?
Issue #48 mention something about it, but I dont understand the core idea:
"To be honest, we have not yet tried parallel loads using SLT SDK, however, the way we have treated the authentication is by using a Managed Identity and generating an access token from Azure AD.
We then stored this access token in SLT cluster memory since it expires after every 24 hours, with each data transfer, we retrieve the access token if within 23 hours else generate a new one and store it again."

[vikasbansal2022]

Thanks @leofrederiksen for reaching out.

I will be happy to connect. Please share you email ID will setup call with you.

Regards,
Vikas

[leofrederiksen]

Thanks,

[vikasbansal2022]

Thanks Leo

Will be addressing this in issue # Error in Importing SAS Key #97

Regards,
Vikas