Yes I am talking about unified push web admin console.

I do not know why I should be forced to use different browser window in order to log in as different user.

Sorry for having possible duplicate issues but anyway:

1) The very first hit of login page after deployment throws exception that I am not authorized. This exception does not make sense to me since I do know I am not logged in yet and hence not authorized to do anything yet. The exception is as follows:

10:32:28,421 ERROR [org.jboss.weld.Bean] (http--127.0.0.1-8080-1) WELD-000019 Error destroying an instance Managed Bean [class org.jboss.aerogear.unifiedpush.jpa.dao.impl.PushApplicationDaoImpl] with qualifiers [@Any @Default] of org.jboss.aerogear.unifiedpush.jpa.dao.impl.PushApplicationDaoImpl@4c4e6453
10:32:28,422 ERROR [org.jboss.ejb3.invocation] (http--127.0.0.1-8080-1) JBAS014134: EJB Invocation failed on component PushApplicationEndpoint for method public javax.ws.rs.core.Response org.jboss.aerogear.unifiedpush.rest.registry.applications.PushApplicationEndpoint.listAllPushApplications(): javax.ejb.EJBException: org.jboss.aerogear.security.exception.AeroGearSecurityException: Not authorized!
... monster stack trace follows

After putting admin:123 another exception is thrown:

10:33:35,230 ERROR [org.jboss.ejb3.invocation] (http--127.0.0.1-8080-1) JBAS014134: EJB Invocation failed on component AuthenticationEndpoint for method public javax.ws.rs.core.Response org.jboss.aerogear.unifiedpush.rest.security.AuthenticationEndpoint.login(org.jboss.aerogear.unifiedpush.users.Developer): javax.ejb.EJBException: org.jboss.aerogear.security.exception.AeroGearSecurityException: Credential has expired
.... monster stack trace follows

Login with various users:

Scenario 1)

Log in as admin in one browser, when trying to log in as admin in the second window, it writes error, looking at error trace it says I am already logged in. So why it does not redirect me directly to the application?

Scenario 2)

Log in as admin in the first window, log in as developer for the first time in the second window, I need to change default password of developer, I do so, I am going to relogin with developer in the second window while I am still logged in as admin in the first one and it says that I am already logged in. How is that possible? I am logged in only as admin, I am not logged in as developer since I just re-enter passwords from to override the default one and I am about to log in as developer for the first time ever.

11:03:17,714 ERROR [org.jboss.ejb3.invocation] (http--127.0.0.1-8080-1) JBAS014134: EJB Invocation failed on component AuthenticationEndpoint for method public javax.ws.rs.core.Response org.jboss.aerogear.unifiedpush.rest.security.AuthenticationEndpoint.login(org.jboss.aerogear.unifiedpush.users.Developer): javax.ejb.EJBException: org.picketlink.authentication.UserAlreadyLoggedInException: active agent: org.picketlink.idm.model.basic.User@de9fe3a0

Regarding submitting wrong password on the screen where I have to change it from the default one:

When I enter two passwords which do not match, error is displayed to me about that. However, when I enter them for the second time, this time both passwords match and I am redirected to re-login page, that error message about non-matching passwords from last screen is still there. I would expect that that message is not visible anymore when I enter these passwords right for the second time.

Very annoying this that there are some files like "unifiedpush.h2.db" and "unifiedpush.lock.db" in my home directory (how it is even possible that application pollutes my home directory) so when I do deploy / undeploy thing I am not able to log in even with default admin:123.

It is quite unpredictable when it comes to login / logout operations with different users since there is quite a lot combinations to try however my biggest concern, besides bugs in mentioned, is that it does not do what I would expect + errors are thrown to console with monster stack trace about obvious things. I do know that I am not authorized to do something. That error could be described in one line and not spanning multiple screens. Debugging the application is not very convenient with the current behaviour.