That's what makes it possible to have multiple automatic interactive documentation interfaces, code generation, etc.

OpenAPI has a way to define multiple security "schemes".

By using them, you can take advantage of all these standard-based tools, including these interactive documentation systems.

OpenAPI defines the following security schemes:

* `apiKey`: an application specific key that can come from:
    * A query parameter.
    * A header.

 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs.internal.smb2.lease;

/**
 * Defines the scope of directory caching for SMB3 directory leasing
 */
public enum DirectoryCacheScope {
    /**
     * Cache only direct children of the directory
     */
    IMMEDIATE_CHILDREN,

    /**

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs.internal.smb2.create;

import jcifs.Encodable;

/**
 * SMB2 Create Context request interface. This interface defines the contract for
 * context data included in SMB2 Create requests.
 *
 * @author mbechler
 *
 */
public interface CreateContextRequest extends Encodable {

    /**
     * Get the name of this create context.

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs.smb;

/**
 * Interface for renewable SMB credentials.
 *
 * This interface defines methods for credentials that can be
 * automatically renewed during long-running operations.
 *
 * @author mbechler
 */
public interface SmbRenewableCredentials extends CredentialsInternal {

    /**

 */
package jcifs.internal.dtyp;

import jcifs.Decodable;

/**
 * Interface for Windows Data Type (DTYP) security information structures.
 * Defines constants and functionality for security information types used in
 * SMB security descriptor operations and access control management.
 *
 * @author mbechler
 */
public interface SecurityInfo extends Decodable {

 */

package jcifs.dcerpc.ndr;

/**
 * Base class for NDR (Network Data Representation) objects used in DCE/RPC communication.
 * This abstract class defines the interface for encoding and decoding NDR data types.
 */
public abstract class NdrObject {

    /**
     * Default constructor for NDR object
     */
    public NdrObject() {
        // Default constructor

 */

package jcifs.smb1.dcerpc.ndr;

/**
 * Base class for NDR (Network Data Representation) objects used in DCE/RPC communication.
 * This abstract class defines the interface for encoding and decoding NDR data types.
 */
public abstract class NdrObject {

    /**
     * Default constructor for NDR object
     */
    public NdrObject() {
        // Default constructor

 */
package jcifs.internal.fscc;

import jcifs.Decodable;
import jcifs.Encodable;

/**
 * Base interface for File System Control Code (FSCC) file information structures.
 * Defines common functionality for various SMB2/SMB3 file information classes used in
 * query and set file information operations, with constants for information levels.
 *
 * @author mbechler
 */

import jcifs.SmbTree;
import jcifs.internal.CommonServerMessageBlockResponse;
import jcifs.internal.Request;

/**
 * Internal SMB tree connection interface providing extended tree management capabilities.
 * Defines methods for internal tree operations and resource management.
 *
 * @author mbechler
 *
 * <p>This interface is intended for internal use.</p>
 */
public interface SmbTreeInternal extends SmbTree {

    /**

import static org.junit.jupiter.api.Assertions.assertTrue;

import org.junit.jupiter.api.Test;
import org.mockito.Mockito;

/**
 * Tests for {@link SmbFilenameFilter}. Since the interface only defines
 * a single method, the tests simply ensure that the lambda expression
 * correctly implements the method and that any exception is propagated.
 */
class SmbFilenameFilterTest {

    @Test