Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEODE-6174: Test REST API with a secured cluster #3255

Merged
merged 5 commits into from Mar 4, 2019

Conversation

pdxrunner
Copy link

Add tests for the create region REST API with a SecurityManager on the cluster.

  • Test without credentails
  • Authentication failure (bad user:password)
  • Authenticated but not authorized
  • Authenticated and Authorized

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

  • Has your PR been rebased against the latest commit within the target branch (typically develop)?

  • Is your initial contribution a single, squashed commit?

  • Does gradlew build run cleanly?

  • Have you written or updated unit tests to verify your changes?

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

Add tests for the create region REST API with a SecurityManager on the cluster.

- Test without credentails
- Authentication failure (bad user:password)
- Authenticated but not authorized
- Authenticated and Authorized
@pdxrunner
Copy link
Author

@Petahhh

}


private static void verifyRegionPersisted(String regionName, String type) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since this test is very similar to the RegionManagementDunitTest, should we just add the security manager to that test and then it should cover all cases.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Certainly could. I just figured on keeping both the secured and unsecured tests as separate entities.

@Petahhh
Copy link
Contributor

Petahhh commented Mar 4, 2019

Looks awesome @pdxrunner

@pdxrunner pdxrunner merged commit 5bef447 into apache:develop Mar 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants