If you add all the auth parameters (–auth S2S –clientid etc…) to the getdata line, then BCCL can renew the token during the transfer.
BCCL getdata credential timeout?
4 Responses
Leave a Reply
You must be logged in to post a comment.
If you add all the auth parameters (–auth S2S –clientid etc…) to the getdata line, then BCCL can renew the token during the transfer.
You must be logged in to post a comment.
Hi Erik, still getting the error.
C:BCCLFeb2025BCCL_2.22.0.267installerclientWindows>BCCL -t getdata -s table=27 -o Item -m mappingItem.mapping.json –auth S2S –clientid @@@@ –clientsecret “@@@@” –tenantid @@@@
Sql table Item, 1000 inserted, 0 updated
Sql table Item, 1000 inserted, 0 updated
Sql table Item, 1000 inserted, 0 updated
Sql table Item, 1000 inserted, 0 updated
Sql table Item, 1000 inserted, 0 updated
Sql table Item, 1000 inserted, 0 updated
Sql table Item, 1000 inserted, 0 updated
An error has occurred: Unauthorized The credentials provided are incorrect
An error has occurred: Unauthorized The credentials provided are incorrect
BCCL assumes that tokens live for 1 hour, and refreshes after 30 minutes. Is your Entra setup to have very short-lived tokens?
How many minutes before the error comes?
… you just try using the bccl.exe from the BCCL3 beta (find it here https://www.hougaard.com/on-premises/bccl/beta ) That one should work better with short lived tokens.