<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: XSOAR Login error when using aws load balancer in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/xsoar-login-error-when-using-aws-load-balancer/m-p/595123#M3538</link>
    <description>&lt;P&gt;Anyone with actual experience with XSOAR running in AWS behind an ELB will have more accurate information than I will as I have never run this type of setup.&lt;BR /&gt;&lt;BR /&gt;Unfortunately, I don't have a concrete answer for you, and you may want to open a ticket with support (PAN, AWS, both?) for assistance with this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can see from your post that you are using an Elastic Load Balancer (ELB) and not an Application Load Balancer (ALB).&amp;nbsp;&lt;BR /&gt;My first guess then is that this could be related to sticky sessions.&lt;BR /&gt;Second, it could be that the ELB is not passing the cookie back to XSOAR properly or in the way XSOAR expects to receive it. I know that there is a restriction on ALB's (which you are not using) which prevents using JWT tokens, but that might be a red-herring in your issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Support will (hopefully) have a better understanding about the authentication methods used by XSOAR and how to troubleshoot to see if this is an AWS issue, an XSOAR issue, or a limitation of the products being used in this way.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Aug 2024 16:11:29 GMT</pubDate>
    <dc:creator>cmcneil</dc:creator>
    <dc:date>2024-08-16T16:11:29Z</dc:date>
    <item>
      <title>XSOAR Login error when using aws load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/xsoar-login-error-when-using-aws-load-balancer/m-p/595074#M3530</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;This is AWS environment.&lt;BR /&gt;I installed XSOAR 6.12 on Private EC2.&lt;BR /&gt;Since it is not accessible from the outside,&lt;/P&gt;
&lt;P&gt;I created a Public Subnet, connected a Load Balancer, and specified the Private EC2 where XSOAR is installed in the target group.&lt;/P&gt;
&lt;P&gt;The Load Balancer DNS address uses the default value.&lt;BR /&gt;(ex. ***-*****-**-1*********.ap-northeast-2.elb.amazonaws.com)&lt;/P&gt;
&lt;P&gt;In this state, XSOAR web UI is connected and the Login page appears.&lt;BR /&gt;However, when I enter my ID and password to log in,&lt;BR /&gt;"Username and password do not match." error occurs on the Web UI screen.&lt;/P&gt;
&lt;P&gt;At first, I thought I entered the ID/PW incorrectly, but after checking XSOAR's server.log, it was not an ID/PW problem.&lt;BR /&gt;The server.log is like this. ===========================================================&lt;BR /&gt;2024-08-16 06:02:36.4868 warning CSRF issue for method : POST [error 'http: named cookie not present'] (source: /builds/GOPATH/src/gitlab.xdr.pan.local/xdr/xsoar/server/web/middleware.go:463)&lt;BR /&gt;================================================================&lt;/P&gt;
&lt;P&gt;I don't know what the problem is.&lt;BR /&gt;Please help me if you have any advice or know how to solve it.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2024 06:10:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/xsoar-login-error-when-using-aws-load-balancer/m-p/595074#M3530</guid>
      <dc:creator>BaeSoungUk</dc:creator>
      <dc:date>2024-08-16T06:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: XSOAR Login error when using aws load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/xsoar-login-error-when-using-aws-load-balancer/m-p/595123#M3538</link>
      <description>&lt;P&gt;Anyone with actual experience with XSOAR running in AWS behind an ELB will have more accurate information than I will as I have never run this type of setup.&lt;BR /&gt;&lt;BR /&gt;Unfortunately, I don't have a concrete answer for you, and you may want to open a ticket with support (PAN, AWS, both?) for assistance with this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can see from your post that you are using an Elastic Load Balancer (ELB) and not an Application Load Balancer (ALB).&amp;nbsp;&lt;BR /&gt;My first guess then is that this could be related to sticky sessions.&lt;BR /&gt;Second, it could be that the ELB is not passing the cookie back to XSOAR properly or in the way XSOAR expects to receive it. I know that there is a restriction on ALB's (which you are not using) which prevents using JWT tokens, but that might be a red-herring in your issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Support will (hopefully) have a better understanding about the authentication methods used by XSOAR and how to troubleshoot to see if this is an AWS issue, an XSOAR issue, or a limitation of the products being used in this way.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2024 16:11:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/xsoar-login-error-when-using-aws-load-balancer/m-p/595123#M3538</guid>
      <dc:creator>cmcneil</dc:creator>
      <dc:date>2024-08-16T16:11:29Z</dc:date>
    </item>
  </channel>
</rss>

