This doesn't really have anything to do with Swing per se...
You just need to create a 'User' object when the user has sucessfully logged in. Then store it somewhere where every listener can get to it through a static method.
How you use this 'User' object is up to you... you can make subclasses of 'User' like 'Guest', 'Operator', 'Admin', etc. and
test based on that inside the action. This is a really simple model... for more complex security requirements (like 'a user can do this action if they are a manager, but only if they are a manager at the location they are trying to affect') you might want to either extend this model or go with a more 'function-based' security model rather than a 'class-based' security model. If security is a big part of your app you might want to make a class that implements ActionListener and that has a lot of built in calls to do security based things.
