<?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 PA 10.2.3, RADIUS Challenge caused timeout even it shows auth success on Monitor in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-10-2-3-radius-challenge-caused-timeout-even-it-shows-auth/m-p/521496#M588</link>
    <description>&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;I have Palo Alto 10.2.3, and also 10.0.3 as a test. I used RADIUS to authenticate to the admin UI, then the RADIUS server sends a challenge, this is being handled normally by 10.0.3 but 10.2.3 seems to timeout although on Monitor it shows successful. Is this a bug? Can someone help me please this is very urgent.&amp;nbsp; Also if I did want to choose a different authentication scheme this is not handled, seems it only handles 1 factor but two factor doesn't work for some unknown reason here. Below are the logs:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2022-11-17 02:42:23.639 +0200 debug: pan_auth_response_process(pan_auth_state_engine.c:4570): Authentication success: &amp;lt;profile: 'RSA_RADIUS_CLOUD', vsys: 'shared', username 'mdawoud'&amp;gt;&lt;BR /&gt;2022-11-17 02:42:23.639 +0200 authenticated for user 'mdawoud'. auth profile 'RSA_RADIUS_CLOUD', vsys 'shared', server profile 'RSA_RADIUS_CLOUD', server address '10.55.55.58', auth protocol 'PAP', reply message 'Authentication succeeded' From: 192.168.100.1.&lt;BR /&gt;2022-11-17 02:42:23.639 +0200 debug: _log_auth_respone(pan_auth_server.c:310): Sent PAN_AUTH_SUCCESS auth response for user 'mdawoud' (exp_in_days=-1 (-1 never; 0 within a day))(authd_id: 7166775411576143886) (reply message 'Authentication succeeded') (return domain 'dawoud')&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: cfgagent_opcmd_callback(pan_cfgagent.c:520): authd: cfg agent received op command from server&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: cfgagent_doop_callback(pan_cfgagent.c:555): received signal to execute for agent: authd&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: pan_authd_opcmd_handler(pan_auth_ops.c:1057): Start executing cmd: 'connection_debug_on'&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: pan_authd_connection_debug_on(pan_auth_ops.c:232): Got protocol-type (null); connetion-id 4294967295; debug-prefix (null)&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 Error: pan_authd_conn_mgmt_enable_debug(pan_authd_conn_mgmt.c:546): Invalid connection context id 33554433 &amp;gt;= total number 2&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: _set_ctxt_debug_on(pan_auth_service_handle.c:986): set debug on for conn_id: 33554433 ; server addr: 10.55.55.50:1812 ; method: RADIUS with debug prefix ''&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 Error: pan_authd_conn_mgmt_enable_debug(pan_authd_conn_mgmt.c:546): Invalid connection context id 33554434 &amp;gt;= total number 2&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: _set_ctxt_debug_on(pan_auth_service_handle.c:986): set debug on for conn_id: 33554434 ; server addr: 10.55.55.50:1812 ; method: RADIUS with debug prefix ''&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: pan_authd_conn_mgmt_enable_debug(pan_authd_conn_mgmt.c:558): conn_id=1 is enabled debugging with prefix ''&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: _set_ctxt_debug_on(pan_auth_service_handle.c:986): set debug on for conn_id: 1 ; server addr: 10.55.55.58:1812 ; method: RADIUS with debug prefix ''&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.</description>
    <pubDate>Thu, 17 Nov 2022 01:16:20 GMT</pubDate>
    <dc:creator>koibito92</dc:creator>
    <dc:date>2022-11-17T01:16:20Z</dc:date>
    <item>
      <title>PA 10.2.3, RADIUS Challenge caused timeout even it shows auth success on Monitor</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-10-2-3-radius-challenge-caused-timeout-even-it-shows-auth/m-p/521496#M588</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;I have Palo Alto 10.2.3, and also 10.0.3 as a test. I used RADIUS to authenticate to the admin UI, then the RADIUS server sends a challenge, this is being handled normally by 10.0.3 but 10.2.3 seems to timeout although on Monitor it shows successful. Is this a bug? Can someone help me please this is very urgent.&amp;nbsp; Also if I did want to choose a different authentication scheme this is not handled, seems it only handles 1 factor but two factor doesn't work for some unknown reason here. Below are the logs:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2022-11-17 02:42:23.639 +0200 debug: pan_auth_response_process(pan_auth_state_engine.c:4570): Authentication success: &amp;lt;profile: 'RSA_RADIUS_CLOUD', vsys: 'shared', username 'mdawoud'&amp;gt;&lt;BR /&gt;2022-11-17 02:42:23.639 +0200 authenticated for user 'mdawoud'. auth profile 'RSA_RADIUS_CLOUD', vsys 'shared', server profile 'RSA_RADIUS_CLOUD', server address '10.55.55.58', auth protocol 'PAP', reply message 'Authentication succeeded' From: 192.168.100.1.&lt;BR /&gt;2022-11-17 02:42:23.639 +0200 debug: _log_auth_respone(pan_auth_server.c:310): Sent PAN_AUTH_SUCCESS auth response for user 'mdawoud' (exp_in_days=-1 (-1 never; 0 within a day))(authd_id: 7166775411576143886) (reply message 'Authentication succeeded') (return domain 'dawoud')&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: cfgagent_opcmd_callback(pan_cfgagent.c:520): authd: cfg agent received op command from server&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: cfgagent_doop_callback(pan_cfgagent.c:555): received signal to execute for agent: authd&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: pan_authd_opcmd_handler(pan_auth_ops.c:1057): Start executing cmd: 'connection_debug_on'&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: pan_authd_connection_debug_on(pan_auth_ops.c:232): Got protocol-type (null); connetion-id 4294967295; debug-prefix (null)&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 Error: pan_authd_conn_mgmt_enable_debug(pan_authd_conn_mgmt.c:546): Invalid connection context id 33554433 &amp;gt;= total number 2&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: _set_ctxt_debug_on(pan_auth_service_handle.c:986): set debug on for conn_id: 33554433 ; server addr: 10.55.55.50:1812 ; method: RADIUS with debug prefix ''&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 Error: pan_authd_conn_mgmt_enable_debug(pan_authd_conn_mgmt.c:546): Invalid connection context id 33554434 &amp;gt;= total number 2&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: _set_ctxt_debug_on(pan_auth_service_handle.c:986): set debug on for conn_id: 33554434 ; server addr: 10.55.55.50:1812 ; method: RADIUS with debug prefix ''&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: pan_authd_conn_mgmt_enable_debug(pan_authd_conn_mgmt.c:558): conn_id=1 is enabled debugging with prefix ''&lt;BR /&gt;2022-11-17 02:42:29.837 +0200 debug: _set_ctxt_debug_on(pan_auth_service_handle.c:986): set debug on for conn_id: 1 ; server addr: 10.55.55.58:1812 ; method: RADIUS with debug prefix ''&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.</description>
      <pubDate>Thu, 17 Nov 2022 01:16:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-10-2-3-radius-challenge-caused-timeout-even-it-shows-auth/m-p/521496#M588</guid>
      <dc:creator>koibito92</dc:creator>
      <dc:date>2022-11-17T01:16:20Z</dc:date>
    </item>
    <item>
      <title>Re: PA 10.2.3, RADIUS Challenge caused timeout even it shows auth success on Monitor</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-10-2-3-radius-challenge-caused-timeout-even-it-shows-auth/m-p/521580#M589</link>
      <description>&lt;P&gt;We rolled back to 10.1.7 and issue resolved. Did someone report this bug before?&amp;nbsp; I don't see it in Release notes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 22:25:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-10-2-3-radius-challenge-caused-timeout-even-it-shows-auth/m-p/521580#M589</guid>
      <dc:creator>koibito92</dc:creator>
      <dc:date>2022-11-17T22:25:08Z</dc:date>
    </item>
  </channel>
</rss>

