• State Not Answered
  • Replies 2 replies
  • Subscribers 3 subscribers
  • Views 256 views
  • Users 0 members are here
Options
Related

Accessing PiWebApi from Azure Kubernetes

larsoleruben

Hi

We are accessing the PiWebAPI using a service written in Python. Works fine. Right now the service is running on an onprem windows server, thus the service user running it is member of the right groups and the Kerberos authentification works fine.

However, we want to move the service to Azure Kubernetes, running in a Linux container.

Have anybody any experience in how to do that and get the right Kerberos token to be able to authenticate?

Any input is highly appreciated.

Parents Reply
  • 0 in reply to Community User

    That's assuming the customer can wait 6 months for the contract to be negotiated with AVEVA.

     

    Outside of 2023, your options are to use Kerberos or Basic, if you're running the latest non-2023 version, 2021 SP3. Now, if you go back to 2019 SP1, you can use the Bearer Authentication method. However, this does require using the deprecated C2WTS and requires an IDP to verify the JWT. Your options depend on your timeline and security requirements - although I'd always recommend using the most secure (which in this case would be 2023 with AVEVA AIM).

     

    That being said, hopefully AVEVA does something to allow users without AVEVA AIM to user Bearer Authentication. It's a standard authentication method and should be supported regardless of which contract a customer has.

Children
No Data