You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by steveloughran <gi...@git.apache.org> on 2015/11/19 16:04:26 UTC

[GitHub] hadoop pull request: HADOOP-12587 Hadoop auth token refused to wor...

GitHub user steveloughran opened a pull request:

    https://github.com/apache/hadoop/pull/48

    HADOOP-12587 Hadoop auth token refused to work without a maxinactive attribute in issued token

    This initial patch is not a fix. This is the patch to diagnose why I cannot submit work to a secure cluster and so identify the change that actually broke things.
    
    I would propose that the max-inactive value is considered optional, defaulting to -1 as the code itself appears to do elsewhere.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/steveloughran/hadoop stevel/HADOOP-12587-max-inactive-auth-token

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hadoop/pull/48.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #48
    
----
commit 6a92ebda2c1bcf5b1eacfd7ee1d687b08699aa92
Author: Steve Loughran <st...@hortonworks.com>
Date:   2015-11-19T15:01:21Z

    HADOOP-12587 Hadoop auth token refused to work without a maxinactive attribute in issued token

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Re: [GitHub] hadoop pull request: HADOOP-12587 Hadoop auth token refused to wor...

Posted by Muhammad Abid <ma...@gmail.com>.
please unsubscribe me from this mailing list.

Thanks

On Thu, Nov 19, 2015 at 10:04 AM, steveloughran <gi...@git.apache.org> wrote:

> GitHub user steveloughran opened a pull request:
>
>     https://github.com/apache/hadoop/pull/48
>
>     HADOOP-12587 Hadoop auth token refused to work without a maxinactive
> attribute in issued token
>
>     This initial patch is not a fix. This is the patch to diagnose why I
> cannot submit work to a secure cluster and so identify the change that
> actually broke things.
>
>     I would propose that the max-inactive value is considered optional,
> defaulting to -1 as the code itself appears to do elsewhere.
>
> You can merge this pull request into a Git repository by running:
>
>     $ git pull https://github.com/steveloughran/hadoop
> stevel/HADOOP-12587-max-inactive-auth-token
>
> Alternatively you can review and apply these changes as the patch at:
>
>     https://github.com/apache/hadoop/pull/48.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
>     This closes #48
>
> ----
> commit 6a92ebda2c1bcf5b1eacfd7ee1d687b08699aa92
> Author: Steve Loughran <st...@hortonworks.com>
> Date:   2015-11-19T15:01:21Z
>
>     HADOOP-12587 Hadoop auth token refused to work without a maxinactive
> attribute in issued token
>
> ----
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastructure@apache.org or file a JIRA ticket
> with INFRA.
> ---
>



-- 
Regards,

Muhammad Abid
http://www.abidshafiq.com
Mobile: +1 (516) 514 6709
Skype: mabidshafiq

[GitHub] hadoop pull request: HADOOP-12587 Hadoop auth token refused to wor...

Posted by steveloughran <gi...@git.apache.org>.
Github user steveloughran closed the pull request at:

    https://github.com/apache/hadoop/pull/48


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---