- Dev Build
- Native Image
- How-to Guides
- Native Image Basics
- Build Overview
- Reachability Metadata
- Optimizations and Performance
- Debugging and Diagnostics
- Dynamic Features
- Accessing Resources
- Certificate Management
- Dynamic Proxy
- Java Native Interface
- JCA Security Services
- URL Protocols
- Interoperability with Native Code
- LLVM Backend
- Workshops and Labs
JCA Security Services in Native Image
The JCA framework uses a provider architecture to access security services such as digital signatures, message digests, certificates and certificate validation, encryption (symmetric/asymmetric block/stream ciphers), key generation and management, and secure random number generation, etc.
To achieve algorithm independence and extensibility it relies on reflection, therefore it requires a custom configuration in Native Image.
By default the Native Image builder uses static analysis to discover which of these services are used (see next section for details).
The automatic registration of security services can be disabled with
Then a custom reflection configuraion file or feature can be used to register the security services required by a specific application.
Note that when automatic registration of security providers is disabled, all providers are, by default, filtered from special JDK caches that are necessary for security functionality.
In this case, you must manually mark used providers with
Security Services Automatic Registration #
The mechanism, implemented in the
com.oracle.svm.hosted.SecurityServicesFeature class, uses reachability of specific API methods in the JCA framework to determine which security services are used.
Each JCA provider registers concrete implementation classes for the algorithms it supports.
Each of the service classes (
KeyStore, etc.,) declares a series of
getInstance(<algorithm>, <provider>) factory methods which provide a concrete service implementation.
When a specific algorithm is requested the framework searches the registered providers for the corresponding implementation classes and it dynamically allocates objects for concrete service implementations.
The Native Image builder uses static analysis to discover which of these services are used.
It does so by registering reachability handlers for each of the
getInstance() factory methods.
When it determines that a
getInstance() method is reachable at run time it automatically performs the reflection registration for all the concrete implementations of the corresponding service type.
Tracing of the security services automatic registation can be enabled with
The report will detail all registered service classes, the API methods that triggered registration, and the parsing context for each reachable API method.
--enable-all-security-services option is now deprecated and it will be removed in a future release.
Provider Registration #
The native image builder captures the list of providers and their preference order from the underlying JVM.
The provider order is specified in the
java.security file under
New security providers cannot be registered at run time; all providers must be statically configured during a native image building.
Provider Reordering at Runtime #
It is possible to reorder security providers at runtime, however only existing provider instances can be used. For example, if the BouncyCastle provider was registered at build time and we wish to insert it at position 1 at runtime:
Provider bcProvider = Security.getProvider("BC"); Security.removeProvider("BC"); Security.insertProviderAt(bcProvider, 1);
The SecureRandom implementations open the
/dev/urandom files which are used as sources for entropy.
These files are usually opened in class initializers.
To avoid capturing state from the machine that runs the Native Image builder these classes need to be initialized at run time.
Custom Service Types #
By default, only services specified in the JCA are automatically registered. To automatically register custom service types, you can use
Note that for automatic registration to work, the service interface must have a
getInstance method and have the same simple name as the service type.
If relying on third party code that doesn’t comply to the above requirements, manual configuration will be required. In that case, providers for such services must explicitly be registered using
Note that these options are only required in very specific cases and should not normally be needed.