You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
\<security>
...
<realm>
<name>demo</name>
<description>Sample realm for file-based authentication</description>
<!-- Include user name in log messages and make visible in JMX beans -->
<user-principal-class>
org.kaazing.gateway.security.auth.config.UserConfig
</user-principal-class>
<authentication>
<http-challenge-scheme>Application Basic</http-challenge-scheme>
...
The text was updated successfully, but these errors were encountered:
cmebarrow
changed the title
OOTB log4j-config.xml file has obsolete content and does not document MaxBackupIndex
OOTB log4j-config.xml file improvements needed (does not document MaxBackupIndex, etc)
Sep 22, 2016
cmebarrow
pushed a commit
to cmebarrow/gateway
that referenced
this issue
Sep 23, 2016
cmebarrow
changed the title
OOTB log4j-config.xml file improvements needed (does not document MaxBackupIndex, etc)
OOTB log4j-config.xml and gateway-config.xml improvements are needed (does not document MaxBackupIndex, etc)
Nov 4, 2016
@sbadugu@robinzimmermann Robin wants to make sure we bump the minor release version (2nd version digit) for this since if customers uptake the updated OOTB log4j-config.xml they will see a change in behavior (no more access.log and proxy.log files generated, up to 2 error.log.x files up to 50MB each instead of a single one up to 10MB).
Our OOTB log4j-config.xml file needs some improvements:
(see also issue #773)
The text was updated successfully, but these errors were encountered: