Your job basically is to write one or more javax.servlet.Filter
that handles incoming requests and act according to whether there’s a
cookie with a SSO token, username+password parameters etc.

It’s assumed that there’s some form of DependencyInjection framework in
place - to get a handle to the SingleSignOnRegistry or the
LdapAuthenticationGateway , you’ll simply have to provide something
like:

About this kata

This “real life” scenario has been used to demonstrate how mocking
(using Mockito) can be useful. We’ve combined it with BDD and JDojo@Gbg
will try to practice TDD using this kata (without mocking) next time
around.

(“Real life” is quoted - proper JEE authentication should be tied into
the container etc etc … The point with this exercise is that it’s
fairly easy to explain how it should work and what needs to be done here
with “real” Java EE API:s, and then focus on the “How to develop” aspect
(TDD), but also to show/talk about the difference between mocking and
stubbing.)