[jira] [Updated] (HADOOP-14687) AuthenticatedURL will reuse bad/expired session cookies

2017-08-22 Thread Jason Lowe (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Lowe updated HADOOP-14687:

   Resolution: Fixed
 Hadoop Flags: Reviewed
Fix Version/s: 2.8.2
   3.0.0-beta1
   2.9.0
   Status: Resolved  (was: Patch Available)

Thanks, Daryn!  I committed this to trunk, branch-2, branch-2.8, and 
branch-2.8.2.

> AuthenticatedURL will reuse bad/expired session cookies
> ---
>
> Key: HADOOP-14687
> URL: https://issues.apache.org/jira/browse/HADOOP-14687
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.6.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
>Priority: Critical
> Fix For: 2.9.0, 3.0.0-beta1, 2.8.2
>
> Attachments: HADOOP-14687.2.trunk.patch, 
> HADOOP-14687.branch-2.8.patch, HADOOP-14687.trunk.patch
>
>
> AuthenticatedURL with kerberos was designed to perform spnego, then use a 
> session cookie to avoid renegotiation overhead.  Unfortunately the client 
> will continue to use a cookie after it expires.  Every request elicits a 401, 
> connection closes (despite keepalive because 401 is an "error"), TGS is 
> obtained, connection re-opened, re-requests with TGS, repeat cycle.  This 
> places a strain on the kdc and creates lots of time_wait sockets.
>  
> The main problem is unbeknownst to the auth url, the JDK transparently does 
> spnego.  The server issues a new cookie but the auth url doesn't scrape the 
> cookie from the response because it doesn't know the JDK re-authenticated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14687) AuthenticatedURL will reuse bad/expired session cookies

2017-08-22 Thread Daryn Sharp (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daryn Sharp updated HADOOP-14687:
-
Attachment: HADOOP-14687.branch-2.8.patch

Conflicts in 2.8 essentially due to logging (2.8 didn't have a logger).

> AuthenticatedURL will reuse bad/expired session cookies
> ---
>
> Key: HADOOP-14687
> URL: https://issues.apache.org/jira/browse/HADOOP-14687
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.6.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
>Priority: Critical
> Attachments: HADOOP-14687.2.trunk.patch, 
> HADOOP-14687.branch-2.8.patch, HADOOP-14687.trunk.patch
>
>
> AuthenticatedURL with kerberos was designed to perform spnego, then use a 
> session cookie to avoid renegotiation overhead.  Unfortunately the client 
> will continue to use a cookie after it expires.  Every request elicits a 401, 
> connection closes (despite keepalive because 401 is an "error"), TGS is 
> obtained, connection re-opened, re-requests with TGS, repeat cycle.  This 
> places a strain on the kdc and creates lots of time_wait sockets.
>  
> The main problem is unbeknownst to the auth url, the JDK transparently does 
> spnego.  The server issues a new cookie but the auth url doesn't scrape the 
> cookie from the response because it doesn't know the JDK re-authenticated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14687) AuthenticatedURL will reuse bad/expired session cookies

2017-08-18 Thread Daryn Sharp (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daryn Sharp updated HADOOP-14687:
-
Attachment: HADOOP-14687.2.trunk.patch

Fixed findbugs.  Return empty string instead of null.  A few style things like 
unused imports.  De-immortalized myself (removed my initials from some log 
lines).

> AuthenticatedURL will reuse bad/expired session cookies
> ---
>
> Key: HADOOP-14687
> URL: https://issues.apache.org/jira/browse/HADOOP-14687
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.6.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
>Priority: Critical
> Attachments: HADOOP-14687.2.trunk.patch, HADOOP-14687.trunk.patch
>
>
> AuthenticatedURL with kerberos was designed to perform spnego, then use a 
> session cookie to avoid renegotiation overhead.  Unfortunately the client 
> will continue to use a cookie after it expires.  Every request elicits a 401, 
> connection closes (despite keepalive because 401 is an "error"), TGS is 
> obtained, connection re-opened, re-requests with TGS, repeat cycle.  This 
> places a strain on the kdc and creates lots of time_wait sockets.
>  
> The main problem is unbeknownst to the auth url, the JDK transparently does 
> spnego.  The server issues a new cookie but the auth url doesn't scrape the 
> cookie from the response because it doesn't know the JDK re-authenticated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14687) AuthenticatedURL will reuse bad/expired session cookies

2017-08-18 Thread Daryn Sharp (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daryn Sharp updated HADOOP-14687:
-
Status: Patch Available  (was: Open)

> AuthenticatedURL will reuse bad/expired session cookies
> ---
>
> Key: HADOOP-14687
> URL: https://issues.apache.org/jira/browse/HADOOP-14687
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.6.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
>Priority: Critical
> Attachments: HADOOP-14687.trunk.patch
>
>
> AuthenticatedURL with kerberos was designed to perform spnego, then use a 
> session cookie to avoid renegotiation overhead.  Unfortunately the client 
> will continue to use a cookie after it expires.  Every request elicits a 401, 
> connection closes (despite keepalive because 401 is an "error"), TGS is 
> obtained, connection re-opened, re-requests with TGS, repeat cycle.  This 
> places a strain on the kdc and creates lots of time_wait sockets.
>  
> The main problem is unbeknownst to the auth url, the JDK transparently does 
> spnego.  The server issues a new cookie but the auth url doesn't scrape the 
> cookie from the response because it doesn't know the JDK re-authenticated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14687) AuthenticatedURL will reuse bad/expired session cookies

2017-08-18 Thread Daryn Sharp (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daryn Sharp updated HADOOP-14687:
-
Attachment: HADOOP-14687.trunk.patch

The most straightforward approach is attaching a cookie handler to the http 
connections to ensure the cookie is captured for all requests including when 
the jdk transparently re-authenticates.  Clients never have to explicitly 
manage the cookie.

> AuthenticatedURL will reuse bad/expired session cookies
> ---
>
> Key: HADOOP-14687
> URL: https://issues.apache.org/jira/browse/HADOOP-14687
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: common
>Affects Versions: 2.6.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
>Priority: Critical
> Attachments: HADOOP-14687.trunk.patch
>
>
> AuthenticatedURL with kerberos was designed to perform spnego, then use a 
> session cookie to avoid renegotiation overhead.  Unfortunately the client 
> will continue to use a cookie after it expires.  Every request elicits a 401, 
> connection closes (despite keepalive because 401 is an "error"), TGS is 
> obtained, connection re-opened, re-requests with TGS, repeat cycle.  This 
> places a strain on the kdc and creates lots of time_wait sockets.
>  
> The main problem is unbeknownst to the auth url, the JDK transparently does 
> spnego.  The server issues a new cookie but the auth url doesn't scrape the 
> cookie from the response because it doesn't know the JDK re-authenticated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org