GUACAMOLE-641: Allow vault implementations to automatically provide tokens based on connection parameters (without YAML mapping).

This commit is contained in:
Michael Jumper committed 2022-01-22 22:25:04 -08:00
1 parent d0bd4b52d6
commit 30f24de808
4 files changed
+73 -16

No files matched your search

@@ -26,10 +26,14 @@ import com.microsoft.azure.keyvault.KeyVaultClient;
import com.microsoft.azure.keyvault.authentication.KeyVaultCredentials;
import com.microsoft.azure.keyvault.models.SecretBundle;
import com.microsoft.rest.ServiceCallback;
import java.util.Collections;
import java.util.Map;
import java.util.concurrent.CompletableFuture;
import java.util.concurrent.Future;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
import org.apache.guacamole.GuacamoleException;
import org.apache.guacamole.protocol.GuacamoleConfiguration;
import org.apache.guacamole.vault.azure.conf.AzureKeyVaultAuthenticationException;
import org.apache.guacamole.vault.azure.conf.AzureKeyVaultConfigurationService;
import org.apache.guacamole.vault.secret.CachedVaultSecretService;
@@ -118,4 +122,10 @@ public class AzureKeyVaultSecretService extends CachedVaultSecretService {
}
@Override
public Map<String, Future<String>> getTokens(GuacamoleConfiguration config)
throws GuacamoleException {
return Collections.emptyMap();
}
}