-
Bug
-
Resolution: Not an Issue
-
P3
-
None
-
1.3.0
-
x86
-
windows_nt
Name: sg39081 Date: 11/02/99
Java configuartion file \jre\1.3\lib\security\java.security is:
----------------
#
# This is the "master security properties file".
#
# In this file, various security properties are set for use by
# java.security classes. This is where users can statically register
# Cryptography Package Providers ("providers" for short). The term
# "provider" refers to a package or set of packages that supply a
# concrete implementation of a subset of the cryptography aspects of
# the Java Security API. A provider may, for example, implement one or
# more digital signature algorithms or message digest algorithms.
#
# Each provider must implement a subclass of the Provider class.
# To register a provider in this master security properties file,
# specify the Provider subclass name and priority in the format
#
# security.provider.<n>=<className>
#
# This declares a provider, and specifies its preference
# order n. The preference order is the order in which providers are
# searched for requested algorithms (when no specific provider is
# requested). The order is 1-based; 1 is the most preferred, followed
# by 2, and so on.
#
# <className> must specify the subclass of the Provider class whose
# constructor sets the values of various properties that are required
# for the Java Security API to look up the algorithms or other
# facilities implemented by the provider.
#
# There must be at least one provider specification in java.security.
# There is a default provider that comes standard with the JDK. It
# is called the "SUN" provider, and its Provider subclass
# named Sun appears in the sun.security.provider package. Thus, the
# "SUN" provider is registered via the following:
#
# security.provider.1=sun.security.provider.Sun
#
# (The number 1 is used for the default provider.)
#
# Note: Statically registered Provider subclasses are instantiated
# when the system is initialized. Providers can be dynamically
# registered instead by calls to either the addProvider or
# insertProviderAt method in the Security class.
#
# List of providers and their preference orders (see above):
#
security.provider.1=sun.security.provider.Sun
security.provider.2=com.sun.rsajca.Provider
#
# Class to instantiate as the system Policy. This is the name of the class
# that will be used as the Policy object.
#
policy.provider=sun.security.provider.PolicyFile
# The default is to have a single system-wide policy file,
# and a policy file in the user's home directory.
policy.url.1=file:${java.home}/lib/security/java.policy
policy.url.2=file:${user.home}/.java.policy
# whether or not we expand properties in the policy file
# if this is set to false, properties (${...}) will not be expanded in policy
# files.
policy.expandProperties=true
# whether or not we allow an extra policy to be passed on the command line
# with -Djava.security.policy=somefile. Comment out this line to disable
# this feature.
policy.allowSystemProperty=true
# whether or not we look into the IdentityScope for trusted Identities
# when encountering a 1.1 signed JAR file. If the identity is found
# and is trusted, we grant it AllPermission.
policy.ignoreIdentityScope=false
#
# Default keystore type.
#
keystore.type=jks
#
# Class to instantiate as the system scope:
#
system.scope=sun.security.provider.IdentityDatabase
#
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageAccess unless the
# corresponding RuntimePermission ("accessClassInPackage."+package) has
# been granted.
package.access=sun.
#
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageDefinition unless the
# corresponding RuntimePermission ("defineClassInPackage."+package) has
# been granted.
#
# by default, no packages are restricted for definition, and none of
# the class loaders supplied with the JDK call checkPackageDefinition.
#
#package.definition=
# JAAS Parameters
login.configuration.provider=com.sun.security.auth.login.ConfigFile
login.config.url.1=file:${user.home}/.java.login.config
--------------------------
${user.home}\.java.login.config is:
SampleLogin {
com.sun.security.auth.module.NTLoginModule REQUIRED debug=true
} ;
----------------------
Given the above configuration the execution of the SampleLogin class produces the following error:
E:\jre\1.3\bin\java com.sun.security.auth.login.SampleLogin
[NTLoginModule]: aborted authentication attempt
Unexpected Exception - unable to continue
javax.security.auth.login.LoginException: java.lang.UnsatisfiedLinkError: no nt in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at com.sun.security.auth.module.NTSystem$1.run(NTSystem.java:167)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.security.auth.module.NTSystem.loadNative(NTSystem.java:164)
at com.sun.security.auth.module.NTSystem.<init>(NTSystem.java:49)
at com.sun.security.auth.module.NTLoginModule.login(NTLoginModule.java:126)
at java.lang.reflect.Method.invoke(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:518)
at javax.security.auth.login.LoginContext.login(LoginContext.java:396)
at com.sun.security.auth.login.SampleLogin.main(SampleLogin.java:59)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:568)
at javax.security.auth.login.LoginContext.login(LoginContext.java:396)
at com.sun.security.auth.login.SampleLogin.main(SampleLogin.java:59)
(Review ID: 96938)
======================================================================