Forum Discussion

casperlow's avatar
casperlow
Helper I
2 years ago
Solved

Gateway authentication expires every two weeks

Hi,

We have an on-prem gateway setup to our Azure Data lake, 
Everything works fine after authenticating my credentials under "Manage Connections and Gateways".
However, I noticed that every two weeks my authentication on the gateway expires and the dataset/semantic model fails to refresh and the error is related the authentication on the gateway. I then have to reauthentication my credentials on the gateway for the dataset/semantic model refreshes fine. 
FYI my credentials have never changed. 

Have this happened to anyone before? Is there a solution for me not to reauthenticate every two weeks?

 

Here's the error Im getting: 

  • Data source error{"error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","pbi.error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The credentials provided for the AzureDataLakeStorage source are invalid. (Source at XXXXX.)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"AzureDataLakeStorage"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"XXXXX"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessUnauthorized"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"AzureDataLakeStorage\",\"path\":\"XXXXX\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessUnauthorized"}}],"exceptionCulprit":1}}} Table: Transaction.
  • Cluster URIWABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net
  • Activity IDb5a81f61-6c93-4421-8701-a83aa58cf8f1
  • Request IDcb27bdb9-17dc-4fc3-ad54-ba5dc0bb55ea
  • Time2024-03-16 21:03:16Z



I would greatly appreciate any input. 

  • casperlow's avatar
    casperlow
    1 year ago

    This has been resolved by updating the gateway and implementing a service principal account. 

    hope that helps. 

5 Replies