92
“Application installed, but may have limited functionality.”
JAD present but is JAR is
unsigned
Authentication can not be performed, will install JAR. MIDlet suite is
treated as untrusted. The following error prompt will be shown,
“Application installed, but may have limited functionality.”
JAR signed but no root certificate
present in the keystore to validate
the certificate chain
Authentication can not be performed. JAR installation will not be
allowed. The following error prompt will be shown, “Root certificate
missing. Application not installed.”
JAR signed, a certificate on the
path is expired
Authentication can not be completed. JAR installation will not be
allowed. The following error prompt will be shown, “Expired
Certificate. Application not installed.”
JAR signed, a certificate rejected
for reasons other than expiration
JAD rejected, JAR installation will not be allowed. The following error
prompt will be shown, “Authentication Error. Application not
installed.”
JAR signed, certificate path
validated but signature verification
fails
JAD rejected, JAR installation will not be allowed. The following error
prompt will be shown, “Authentication Error. Application not
installed.”
Parsing of security attributes in
JAD fails
JAD rejected, JAR installation will not be allowed. The following error
prompt will be shown, “Failed Invalid File.”
JAR signed, certificate path
validated, signature verified
JAR will be installed. The following prompt will be shown, “Installed.”
Table 27 Summary of MIDlet suite verification
Carrier Specific Security Model
The MIDP 2.0 security model will vary based on carrier requests. Contact the carrier for
specifics.
Bound Certificates
Bound certificates enable an efficient process to aid developers in the MIDlet
development and testing phase when working with signed applications. Currently the
delay for the developer occurs because specific flex files need to be created for each
developer and for each domain being tested.
