The following diagram illustrates the overall security solution we're going to set up and use in this chapter:
Now let's walk through the actions involved.
A visitor clicks on the Sign-up button and submits the form to create a new user.
A JavaBean will interact with the JPA object and create the entry on the database.
Concurrently, this JavaBean publishes a message on the JMS queue, possibly a protected WebLogic resource.
Later, a Message Driven Bean (MDB) listening on the queue reads the message and submits the user information to the LDAP server, completing the user-provisioning process.
Due to the protected resource feature of the WebLogic server, this JMS queue can't be used by other systems, unless of course they match the security policy that will be created to protect the JMS queue.
Now that the solution is clear, let's do the implementation starting with the database step.