Not able to get the Correlation cookie in Response when posting back to /signin-oidc after migrating from app service to AKS

Prem Jha 1 Reputation point
2023-01-10T15:03:27.053+00:00

Hi,

when i am trying to do the signin-oidc from akamai it is giving correct correlation cookie in response when i am trying to do from Azure app service.

![277983-image.png][1]

when i am doing the same thing from aks in azure it is sending the request to the akamai correctly but it is not getting correlation cookie in response

![277945-image.png][2]

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,119 questions
No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Akram Kathimi 396 Reputation points Microsoft Employee
    2023-01-11T08:55:08.8566667+00:00

    Hi @Prem Jha ,

    It sounds like you are running into an issue with the Akamai OpenID Connect (OIDC) integration when running your application on Azure Kubernetes Service (AKS) compared to when running it on Azure App Service. The issue you are describing, specifically the missing correlation cookie in the response, could be caused by a number of things. Without more information about the specific configurations and settings you have in place, it's difficult to say for certain what the root cause of the problem might be.

    Some things to consider when troubleshooting this issue include:

    • Checking the request and response headers to see if there are any differences between the AKS and App Service requests.
    • Verifying that the same configurations and settings are being used for the Akamai OIDC integration on both the AKS and App Service deployments.
    • Checking the application logs for any error messages or other relevant information.
    • Making sure the AKS have the same firewall rules as app services (if any).
    • Also, check for the browser used for accessing the application. Some browsers behave differently for this.

    It might be useful to compare the differences between the working App service and non-working AKS to help identify any differences. And also, to reach out to Akamai Support for assistance in troubleshooting this issue. They may be able to provide more information on what might be causing the problem and how to resolve it.

    Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.