public final class SubjectDelegationPermission extends BasicPermission
Permission required by an authentication identity to perform operations on behalf of an authorization identity.
A SubjectDelegationPermission contains a name (also referred to as a "target name") but no actions list; you either have the named permission or you don't.
The target name is the name of the authorization principal
 classname followed by a period and the authorization principal
 name, that is
 "PrincipalClassName.PrincipalName".
An asterisk may appear by itself, or if immediately preceded by a "." may appear at the end of the target name, to signify a wildcard match.
For example, "*", "javax.management.remote.JMXPrincipal.*" and
 "javax.management.remote.JMXPrincipal.delegate" are valid target
 names. The first one denotes any principal name from any principal
 class, the second one denotes any principal name of the concrete
 principal class javax.management.remote.JMXPrincipal
 and the third one denotes a concrete principal name
 delegate of the concrete principal class
 javax.management.remote.JMXPrincipal.
| Constructor | Description | 
|---|---|
| SubjectDelegationPermission(String name) | Creates a new SubjectDelegationPermission with the specified name. | 
| SubjectDelegationPermission(String name,
                           String actions) | Creates a new SubjectDelegationPermission object with the
 specified name. | 
equals, getActions, hashCode, implies, newPermissionCollectioncheckGuard, getName, toStringpublic SubjectDelegationPermission(String name)
name - the name of the SubjectDelegationPermissionNullPointerException - if name is
 null.IllegalArgumentException - if name is empty.public SubjectDelegationPermission(String name, String actions)
name - the name of the SubjectDelegationPermissionactions - must be null.NullPointerException - if name is
 null.IllegalArgumentException - if name is empty
 or actions is not null. Submit a bug or feature 
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
 Copyright © 1993, 2025, Oracle and/or its affiliates.  All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.