DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Key ML Classification Metrics You Need to Understand
  • Diagnosing Test Failures at Scale: Correlating Execution Evidence Across Ephemeral Runners
  • AI-Powered CI Test Failure Triage
  • When a Coding Agent Fixes the Test Instead of the Bug

Trending

  • Build Production-Ready AI Phone Agents: Infrastructure, Models, and Telephony
  • The Pipeline Failed, But the Infrastructure Changed
  • AI-Assisted Refinement Preparation
  • Spring Security JWT Validation Best Practices

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Testing, Tools, and Frameworks
  4. Mocking SecurityContext in Jersey Tests

Mocking SecurityContext in Jersey Tests

Jersey can be used to write integration tests for REST APIs. In this tutorial, you'll learn how to mock a SecurityContext in your tests.

By 
Sandra Parsick
·
Apr. 02, 18 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
9.2K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

Jersey has a great possibility to write integration tests for REST APIs, written with Jersey. Just extend the class JerseyTest and go for it.

I ran into an issue where I had to mock a SecurityContext so that the SecurityContext includes a special UserPrincipal. The challenge is that Jersey wraps the SecurityContext in an own class SecurityContextInjectee in tests. So I have to add my SecurityContext Mock to this Jersey's wrapper class. Let me demonstrate it in an example.

Let say I have the following Jersey Resource:

@Path("hello/world")
public class MyJerseyResource {

 @GET
 public Response helloWorld(@Context final SecurityContext context) {
  String name = context.getUserPrincipal().getName();
  return Response.ok("Hello " + name, MediaType.TEXT_PLAIN).build();
 }

}

In my test, I have to mock the SecurityContext, so that a predefined user principal can be used during the tests. I use Mockito as mocking framework. My mock looks like the following one

final SecurityContext securityContextMock = mock(SecurityContext.class);
when(securityContextMock.getUserPrincipal()).thenReturn(new Principal() {
 @Override
 public String getName() {
  return "Alice";
 }
});

For adding this mocked SecurityContext to the wrapper class SecurityContextInjectee, I have to configure a ResourceConfig with a modified ContainerRequestContext in my Jersey Test. The mocked SecurityContext can be set in this modified ContainerRequestContext and then it will be used in the wrapper class:

@Override
public Application configure() {
 final SecurityContext securityContextMock = mock(SecurityContext.class);
 when(securityContextMock.getUserPrincipal()).thenReturn(new Principal() {
  @Override
  public String getName() {
   return "Alice";
  }
 });

 ResourceConfig config = new ResourceConfig();
 config.register(new ContainerRequestFilter() {
  @Override
  public void filter(final ContainerRequestContext containerRequestContext) throws IOException {
   containerRequestContext.setSecurityContext(securityContextMock);
  }
 });
 return config;
}

Then, the whole test for my resource looks like the following one:

public class MyJerseyResourceTest extends JerseyTest {

 @Test
 public void helloWorld() throws Exception {
  Response response = target("hello/world").request().get();

  assertThat(response.getStatus()).isEqualTo(HttpStatus.SC_OK);
  assertThat(response.getEntity()), isEqualTo("Hello Alice");
 }

 @Override
 public Application configure() {
  final SecurityContext securityContextMock = mock(SecurityContext.class);
  when(securityContextMock.getUserPrincipal()).thenReturn(new Principal() {
   @Override
   public String getName() {
    return "Alice";
   }
  });

  ResourceConfig config = new ResourceConfig();
  config.register(new ContainerRequestFilter() {
   @Override
   public void filter(final ContainerRequestContext containerRequestContext) throws IOException {
    containerRequestContext.setSecurityContext(securityContextMock);
   }
  });
  return config;
 }

Do you have a smarter solution for this problem? Let me know it and write a comment below.

Testing

Published at DZone with permission of Sandra Parsick. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Key ML Classification Metrics You Need to Understand
  • Diagnosing Test Failures at Scale: Correlating Execution Evidence Across Ephemeral Runners
  • AI-Powered CI Test Failure Triage
  • When a Coding Agent Fixes the Test Instead of the Bug

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook