Can login, but roles are not assigned
I have two setups configured identically. One is clustered with the cluster profile, the other is not clustered using the development profile. On the dev profile, everything is fine. On the cluster, user's can login but their roles are not assigned.
Here's my setup:
When logging in, the login is processed, but the user gets a 403 error when trying to access a resource that they should have access to.
I know that the login is being processed because the user is forwarded onto the restricted resource they were requesting. If the login didn't process (bad credentials) the user is correctly shot off to the error logging in page.
I see the following show up in the logs for each of the security roles defined in web.xml:
Log Level: WARNING
Name-Value Pairs: _ThreadID=28;_ThreadName=RMI TCP Connection(1468)-22.214.171.124;_RequestID=44ea8886-a3c0-494f-8857-f9ae6cb4d207;
Record Number: 4356
Complete Message: No Principals mapped to Role [admin]
Is there anything specific to JDBCRealm in a clustered environment? Why does an identical setup work with the development profile and not clustered? Why could the roles not be assigned despite the login processing successfully?
Whe I first used glassfish I had this problem, but that was with the development profile and was easily solved by adding the security-role-mappings in sun-web.xml. Why are the security-role mappings in sun-web.xml ignored in a clustered environment?