# `net.jini.security`
Apache River v3.0.0 Release Notes

### Description

The `net.jini.security` package and its subpackages provide abstractions and facilities for managing security.

### Changes since the v2.2.0 release

- [RIVER-334] - jre 6 Policy issues

### Changes since the v2.1.1 release

None

### Changes since the v2.0.1 release

New proxy preparer

  A new proxy preparer class, `VerifyingProxyPreparer`, has been added. In contrast to `BasicProxyPreparer`, this new preparer always verifies that proxies are trusted, and permits full control over the context elements used during trust verification, the class loader used to find trust verifiers, and the principals used to scope dynamic permission grants. In particular, it can be used to specify a `BasicUntrustedObjectSecurityContext` context element for controlling the operation of `ProxyTrustVerifier` (see below).

Trust verification restriction

  `ProxyTrustVerifier` has been changed so that, by default, when attempting to obtain a bootstrap proxy, operations on untrusted objects are performed in a restricted security context that limits the permissions of unprivileged code (meaning code that does not use some form of `doPrivileged`) to just the permissions that have been granted to all code. In most cases this default will not cause problems, but there are cases where it will. In particular, if you are trying to verify a proxy that uses activation, and a remote call to activate the service is required to obtain the bootstrap proxy, the remote call will now fail due to lack of a `SocketPermission` (unless you have granted broad `connect` `SocketPermission` to all code, which is generally undesirable). To make such a deployment work, you need to provide a `BasicUntrustedObjectSecurityContext` context element that specifies which additional permissions unprivileged code is permitted to exercise (provided the code has already been granted those permissions). This is aimed in particular at specifying the permissions that local code (or already trusted code) is permitted to exercise. For example, you would specify `SocketPermission` to connect to whatever hosts and ports can be used for activation. You can use `VerifyingProxyPreparer` (see above) to specify such a context element.

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.