You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by DmitriyGovorukhin <gi...@git.apache.org> on 2016/10/17 15:22:18 UTC

[GitHub] ignite pull request #1166: Ignite security processor test

GitHub user DmitriyGovorukhin opened a pull request:

    https://github.com/apache/ignite/pull/1166

    Ignite security processor test

    

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

    $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11476

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

    https://github.com/apache/ignite/pull/1166.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 #1166
    
----
commit 234c6cacd3a97c8eaf48dbc29ca3eaed4341581c
Author: Dmitriy Govorukhin <dm...@gmail.com>
Date:   2016-10-06T14:39:27Z

    ignite-gg-11476 Add an option to always authenticate local node

commit b075cbf8367a7e7b2ab2c6c5d0435e2bd6e3e570
Author: Dmitriy Govorukhin <dg...@gridgain.com>
Date:   2016-10-12T18:14:12Z

    ignite-gg-11476 test for secr processor

commit a9fe095be53e9e979243b7de3c13bebb590b930e
Author: Dmitriy Govorukhin <dg...@gridgain.com>
Date:   2016-10-14T09:15:04Z

    ignite-gg-11476 update after review

commit 59df9d913966bb3f9b971d41a53ddb6b0cb18981
Author: Dmitriy Govorukhin <dg...@gridgain.com>
Date:   2016-10-14T09:27:31Z

    ignite-gg-11476 rename arg and javadoc

commit e898fd5805f22bf189fe7e5a5fac4de3bd50902e
Author: Dmitriy Govorukhin <dg...@gridgain.com>
Date:   2016-10-14T09:31:03Z

    ignite-gg-11476 small refactor

commit 09d9a2d8a366f89aecc34b6702642786a0564ab3
Author: Dmitriy Govorukhin <dg...@gridgain.com>
Date:   2016-10-17T10:32:19Z

    ignite-gg-11476 test update, add to suit

commit 2c9a5ada55cb9bf618a7e1467efc1e634c1d9f97
Author: Dmitriy Govorukhin <dg...@gridgain.com>
Date:   2016-10-17T15:20:58Z

    ignite-gg-11476 fail node if security is different

----


---
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.
---