<groupId>org.jline</groupId>
      <artifactId>jline-terminal-ffm</artifactId>
    </dependency>

    <!-- (legacy) DI annotations -->
    <dependency>
      <groupId>javax.inject</groupId>
      <artifactId>javax.inject</artifactId>
    </dependency>
    <dependency>
      <groupId>javax.annotation</groupId>
      <artifactId>javax.annotation-api</artifactId>
    </dependency>

    <!-- DI Runtime -->

        srvsvc.ShareInfoCtr1 shareInfoCtr1 = new srvsvc.ShareInfoCtr1();
        shareInfoCtr1.count = 2;
        shareInfoCtr1.array = new srvsvc.ShareInfo1[] { shareInfo1, shareInfo2 };

        // Inject the ShareInfoCtr1 using reflection
        Field infoField = srvsvc.ShareEnumAll.class.getDeclaredField("info");
        infoField.setAccessible(true);
        infoField.set(msrpcShareEnum, shareInfoCtr1);

        DcerpcPipeHandle handle = mock(DcerpcPipeHandle.class);

        // Inject the binding using reflection
        Field bindingField = DcerpcHandle.class.getDeclaredField("binding");
        bindingField.setAccessible(true);
        bindingField.set(handle, mockDcerpcBinding);

        // Inject the CIFSContext using reflection
        Field tcField = DcerpcHandle.class.getDeclaredField("transportContext");

        // Setup the mock pipe and its input stream
        mockPipe.pipeIn = mockPipeIn;
        // The 'lock' field in TransactNamedPipeInputStream needs to be a real object for synchronization
        mockPipeIn.lock = new Object();

        byte[] buffer = new byte[10];
        int bufferIndex = 0;
        int len = 10;

        // Call the method to be tested

`get_current_user` will use a (fake) utility function we created, that takes a token as a `str` and returns our Pydantic `User` model:

{* ../../docs_src/security/tutorial002_an_py310.py hl[19:22,26:27] *}

## Inject the current user { #inject-the-current-user }

So now we can use the same `Depends` with our `get_current_user` in the *path operation*:

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

            super(witnessServer, context, rpcClient);
        }

        // TestWitnessClient can use the parent implementation now since we inject the mock RPC client
    }

	osMetricStat
	osMetricAccess
	osMetricCreate
	osMetricReadDirent
	osMetricFdatasync
	osMetricSync

	// .... add more

	osMetricLast
)

var globalOSMetrics osMetrics

func init() {
	// Inject metrics.
	ioutilx.OsOpenFile = OpenFile
	ioutilx.OpenFileDirectIO = OpenFileDirectIO
	ioutilx.OsOpen = Open
}

type osMetrics struct {
	// All fields must be accessed atomically and aligned.

        // This requires Mockito 3.4.0+ for MockedStatic
        // For simplicity, we'll assume Crypto.getMD5() is static and mock it.
        // If it's not static, we'd need to inject it or mock the class that provides it.
        try (MockedStatic<Crypto> mockedCrypto = mockStatic(Crypto.class)) {
            mockedCrypto.when(Crypto::getMD5).thenReturn(mockMd5);
        }
    }

    @Test

            transportContextField.setAccessible(true);
            transportContextField.set(ntlmServlet, cifsContext);
        } catch (Exception e) {
            throw new RuntimeException("Failed to inject mock CIFSContext", e);
        }

        when(cifsContext.getTransportPool()).thenReturn(transportPool);
        when(cifsContext.getNameServiceClient()).thenReturn(nameServiceClient);

And then, that system (in this case **FastAPI**) will take care of doing whatever is needed to provide your code with those needed dependencies ("inject" the dependencies).

This is very useful when you need to:

* Have shared logic (the same code logic again and again).
* Share database connections.
* Enforce security, authentication, role requirements, etc.