Setting up a Caller Principal in an Arquillian test

[woelfle]

Hi,

we are using Arquillian to test our business layer. It works pretty well. Thanks for that great framework

Currently I am writing some permission tests where I want to ensure that certain business methods can be invoked only if the current user (derived form the caller principal of the SessionContext) has sufficient permissions. The SessionContext is injected into a StatelessSession Bean in the business layer via a @Resource annotation. When running the Arquillian Unit test the injected SessionContext property is null.

How can I simulate a user login in an Arquillian unit test so that the SessionContext is created?

Best regards,

Thomas

[aslak]

Arquillian currently has no built in helper support for ejb security, even tho it's on our list.

But ALR has some code testing ejb security in his upcoming EJB3 Book using Arquillian.

http://community.jboss.org/wiki/Chapter15-SecurityandSchoolEJBAccess

Basically do a manual login using a new InitialContext() and set SECURITY_PRINCIPAL and SECURITY_CREDENTIALS. Then use that Context to lookup your EJBs.

If your interested in helping prototyping some secure context integration for Arquillian please let me know..

[dan.j.allen]

This would make a good FAQ.

[meindert.hoving]

to set the context I add @OverProtocol("Servlet 3.0") to the @Deployment

to set the 'CallerPrincipal' I use the following code in my Arquilian test:

@EJB private MDocumentListController mDocumentListController;

  @Before

  public void init() throws NamingException {

  SecurityClient client;

  try {

      client = SecurityClientFactory.getSecurityClient();

      client.setSimple("[username]", "[password]");

  try {

      client.login();

  } catch (LoginException e) {

    e.printStackTrace();

  }

  } catch (Exception e1) {

  e1.printStackTrace();

  }