AnsweredAssumed Answered

PI AF Connectivity issue. Ensuring the impersonated client user can be delegated to the server.

Question asked by Dava on Aug 3, 2018
Latest reply on Aug 6, 2018 by gregor

Hi all,

I've been searching and I found severals questions related to the delegated to the server.
Cannot connect to server 'ServerName'. Please examine connectivity to the remote PI AF Server as well as ensuring the impersonated client user can be delegated to the server.

 

But most of all are related to the PI Web API application. So, that is why I'm posting this question.

 

I develop a  web asp.net MVC application, to connect to PI and display information. Using the PI AFSDK and the impersonation feature in Asp .Net
We are testing it in  network architecture with 3 boxes (servers):

1) PI AF
2) PI server (archives)
3) The IIS server with the web app.

 

The issue, I'm having is when I try to impersonate an user launching the web app in any of the server.
Cannot connect to server 'ServerName'. Please examine connectivity to the remote PI AF Server as well as ensuring the impersonated client user can be delegated to the server.

 

Checking other questions like:
https://pisquare.osisoft.com/message/97464-re-online-training-programming-in-pi-web-api-online-course-april-2017-questio…

and

https://pisquare.osisoft.com/community/developers-club/blog/2017/03/17/the-pi-developers-club-pod-uc-2017#comment-10672 

 

Talk about the issue is related to Kerberos Delegation and the PI AF service (I'm using the NT SERVICE\AFService).

Honestly I'm lost, I want to understand if the issue is like and PI AF configuration to do.
Or is more IT configuration in the domain (active directory)

 

My apologies is the question sounds like a old conversation but , most of the anwser are related to the web API.
And I'm not using it

 

 

 

Regards

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Outcomes