public void testCreateProviderAuto() {
        RdmaProvider provider = RdmaProviderFactory.createProvider("auto");
        assertNotNull(provider, "Auto provider selection should return a provider");
        assertTrue(provider.isAvailable(), "Returned provider should be available");
    }

    @Test
    public void testCreateProviderTcp() {
        RdmaProvider provider = RdmaProviderFactory.createProvider("tcp");

        // test that it consistently returns null for any input
        assertNull(invokeMethod(provider, "findOnMainSchema", "TestClassification"));
        assertNull(invokeMethod(provider, "findOnMainSchema", ""));
        assertNull(invokeMethod(provider, "findOnMainSchema", "Some.Classification"));
        assertNull(invokeMethod(provider, "findOnMainSchema", "Project.TestClassification"));
    }

        // Try providers in order of preference
        List<RdmaProvider> providers = Arrays.asList(new DisniRdmaProvider(), // InfiniBand/RoCE - highest performance
                new TcpRdmaProvider() // TCP fallback - always available
        );

        for (RdmaProvider provider : providers) {
            if (provider.isAvailable()) {
                log.info("Selected RDMA provider: {}", provider.getProviderName());

This provider might be charging you per request, and calling it might take some extra time than if you had a fixed mock user for tests.

You probably want to test the external provider once, but not necessarily call it for every test that runs.

In this case, you can override the dependency that calls that provider, and use a custom dependency that returns a mock user, only for your tests.

        JavaToolchainImpl jtc = new DefaultJavaToolChain(model, logger);

        // populate the provides section
        Properties provides = model.getProvides();
        for (Entry<Object, Object> provide : provides.entrySet()) {
            String key = (String) provide.getKey();
            String value = (String) provide.getValue();

            if (value == null) {
                throw new MisconfiguredToolchainException(

| [OpenJSSE]       |         | ✅           | [OpenJDK]       | OpenJDK backport.                                            |
| [Corretto]       | ✅      | ✅           | [OpenSSL]       | Amazon's high-performance provider. [Tracking bug.][bug5592] |

All providers support HTTP/1.1 and TLSv1.2.

- Removed the last remaining in-tree gcp cloud provider and credential provider.
  Please use the external cloud provider and credential provider from https://github.com/kubernetes/cloud-provider-gcp
  instead. ([#124519](https://github.com/kubernetes/kubernetes/pull/124519), [@dims](https://github.com/dims)) [SIG API Machinery, Apps, Auth, Autoscaling, Cloud Provider, Instrumentation, Network, Node, Scheduling, Storage and Testing]

     *
     * This method handles SSO logout requests, coordinating with the SSO provider
     * to properly terminate the user's SSO session. It may involve redirecting
     * to the SSO provider's logout endpoint or performing local logout operations.
     *
     * @return ActionResponse directing to the logout page or SSO provider logout endpoint
     */
    @Execute
    public ActionResponse logout() {

    // Convenience methods for testing

    /**
     * Unsafe cast of the given entry to {@code E}, the type of the specific {@link InternalEntry}
     * implementation type.
     *
     * <p>This method is provided as a convenience for tests. Otherwise they'd need to be
     * knowledgeable about all the implementation details of our type system trickery.
     */
    abstract E castForTesting(InternalEntry<K, V, ?> entry);

**We recommend setting `policy` as a custom claim for the JWT service provider follow [here](https://docs.wso2.com/display/IS550/Configuring+Claims+for+a+Service+Provider) and [here](https://docs.wso2.com/display/IS550/Handling+Custom+Claims+with+the+JWT+Bearer+Grant+Type) for relevant docs on how to configure claims for a service provider.**

### 5. Setup MinIO with OpenID configuration URL