import jcifs.CIFSContext;
import jcifs.CIFSException;

/**
 * Unified authentication provider interface for SMB authentication
 *
 * This interface provides a consistent authentication mechanism across
 * SMB1, SMB2, and SMB3 protocols, addressing the issue of multiple
 * scattered authentication implementations.
 */
public interface AuthenticationProvider {

    /**
     * Authentication type enumeration
     */
    enum AuthType {

Vamos a crear una dependencia `get_current_user`.

¿Recuerdas que las dependencias pueden tener sub-dependencias?

`get_current_user` tendrá una dependencia con el mismo `oauth2_scheme` que creamos antes.

De la misma manera que estábamos haciendo antes en la *path operation* directamente, nuestra nueva dependencia `get_current_user` recibirá un `token` como un `str` de la sub-dependencia `oauth2_scheme`:

{* ../../docs_src/security/tutorial002_an_py310.py hl[25] *}

{* ../../docs_src/dependencies/tutorial007.py hl[3,5] *}

## Sub-dependencies with `yield` { #sub-dependencies-with-yield }

You can have sub-dependencies and "trees" of sub-dependencies of any size and shape, and any or all of them can use `yield`.

import java.nio.charset.StandardCharsets;

import jcifs.internal.SMBProtocolDecodingException;
import jcifs.internal.util.SMBUtil;

/**
 * File System Control Code (FSCC) structure for File Rename Information.
 * Used in SMB2/SMB3 set file information operations to rename files or directories,
 * with support for specifying whether to replace existing files with the same name.
 *
 * @author mbechler
 */

 */
package jcifs.internal.smb2.lease;

import java.security.SecureRandom;
import java.util.Arrays;

/**
 * SMB2 Lease Key
 *
 * Represents a 16-byte lease key used to identify leases in SMB2/SMB3
 * MS-SMB2 2.2.13.2.8
 */
public class Smb2LeaseKey {

    private final byte[] key;
    private static final SecureRandom RANDOM = new SecureRandom();
    private static final int LEASE_KEY_SIZE = 16;

    /**

For example, let's say you have 4 API endpoints (*path operations*):

* `/items/public/`
* `/items/private/`
* `/users/{user_id}/activate`
* `/items/pro/`

then you could add different permission requirements for each of them just with dependencies and sub-dependencies:

```mermaid
graph TB

 * 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.
 */
package org.codelibs.core.beans.impl.sub;

/**
 * @author koichik
 */
class MogeBeanImpl implements MogeBean {

    String name;

    /**
     *
     */
    public MogeBeanImpl() {
    }

    /**
     * @param name

Por ejemplo, digamos que tienes 4 endpoints de API (*path operations*):

* `/items/public/`
* `/items/private/`
* `/users/{user_id}/activate`
* `/items/pro/`

entonces podrías agregar diferentes requisitos de permiso para cada uno de ellos solo con dependencias y sub-dependencias:

```mermaid
graph TB

 * 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.
 */
package org.codelibs.core.beans.impl.sub;

/**
 * @author koichik
 */
public class MogeBeanFactory {

    /**
     * @param name
     * @return MogeBean
     */
    public static MogeBean create(final String name) {

        // Assert
        assertEquals(DialectVersion.SMB202, dialect);
        verify(negotiationResponse).getSelectedDialect();
    }

    @Test
    @DisplayName("Test getSelectedDialect returns SMB3")
    void testGetSelectedDialectSMB3() {
        // Arrange
        when(negotiationResponse.getSelectedDialect()).thenReturn(DialectVersion.SMB311);

        // Act