Security Debugging
The Java security packages include
debugging
code that you can enable via a system property. The property in
question is
java.security.debug
, and it may be set to the following
values:
- all
Turn on all the debugging options.
- access
Trace all calls to the
checkPermission( )method of the access controller. This allows you to see which permissions your code is requesting, which calls are succeeding, and which ones are failing.This option has the following sub-options. If no sub-option is specified, then all are in force:
- stack
Dump the stack every time a permission is checked.
- failure
Dump the stack only when a permission is denied.
- domain
Dump the protection domain in force when a protection is checked.
- jar
When processing a signed jar file, print the signatures in the file, their certificates, and the classes to which they apply.
- policy
Print information about policy files as they are parsed, including their location in the filesystem, the permissions they grant, and the certificates they use for signed code.
- scl
Print information about the permissions granted directly by a secure class loader (rather than granted through a policy file).
These options should be given as a comma-separated list (including
the sub-options for the access option). For example, to see the
permissions granted by the secure class loader and see a stack trace
when a permission check fails, you would specify
-Djava.security.debug=scl,access,failure on the
command line.
JSSE extends this facility ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access