Forum Discussion
Skilled SharerGetToken: Failed to get token authenticator for auth type: ServicePrincipal
Hi.
I have some Data Pipelines with a Semantic Model refresh activity, authenticating with Service Principal. One day, it stopped working, and it shows the following error since then:
I've created a new Data Pipeline with just Semantic Model refresh activity, I've configured it and still the same error. If I authenticate with my organizational account, it works, but I need to authenticate by Service Principal.
The PowerBIDatatsets connection that I'm using is correct, I've checked it in connections list. What does this error mean?
Hi amaaiia ,
We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.Best Regards,
Adamk Kong
6 Replies
- NandanHegde
Super User
can you confirm whether the client secret is still valid for the client ID? Meaning it has not expired
amaaiiaHi,
I know is valid because of two reasons:
1. When I create a new connection using these keys I don't have any errors. For example, If I change a character in the secret, it returns an error message that is not valid.
2. I have another SQL Server connection created to access data in a Lakehouse as data connection for semantic model, using service principal authentication, and it works.
Hi amaaiia ,
Check the logs for any other error messages or detailed information that may help provide more insight into the problem.
Also check if a similar solution as below works for you.Best Regards,
Adamk KongIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- amaaiia
Where can I get more logs? The pipeline is as simple as this:
The activity is configured as follows:
And the connection:
Notice the connection is ok, because if I manually change the key to a no valid key (just to test), I get this error:
So yes, the client id and key are VALID.
Hi amaaiia ,
We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.Best Regards,
Adamk Kong
