I would like my Tomcat instance to authenticate different roles differently.
E.g., admins must use SSL client auth, while regular users use HTTP basic
authentication over SSL. This seems like a routine requirement, but it's
unsupported in Tomcat 6 (or 7).
I have a workaround -- use an Apache
Can anybody reproduce the bug I'm getting in Tomcat 6.0.29, or is it just me?
I'm trying to access a DataSource via JNDI from a ServletContextListener. I
find that my InitialContext has no bindings at all in the
ServletContextListener.contextInitialized() method. It makes no difference
I guess the maintainers know what they're doing, because my original DataSource
problem turns out to be a configuration problem. I still don't know why the
Eclipse project fails for me, but I'm assuming it's some kind of deployment
problem.
Thanks, case closed,
--Steve
From: Steve Mitchell
]
connectionPassword=[]
userTable=USERS userNameCol=SIGNON_ID
userCredCol=CREDENTIAL
userRoleTable=ENTITLEMENTS
roleNameCol=ENTITLEMENT_NAME
/
Thanks,
Steve
Chris wrote:
Steve,
Steve Mitchell wrote:
I'm using a JDBC realm with a site and sometimes
I'm using a JDBC realm with a site and sometimes when you try to access a
secured resource you get a blank page after logging in. You have to refresh
the page to get the secured resource to appear. After that everything works
great. I'm using SSL now, but this happened before I was using SSL.
] jk_map_read_property::jk_map.c (432): The attribute '
worker.loadbalancer.balanced_workers' is deprecated - please check the
documentation for the correct replacement.
Suggestions?
Steve Mitchell
http://www.ByteworksInc.com
