Hello,
I have the key "azure.activedirectory.b2c.client-id" stored in the azure keyvault
as 'azure-activedirectory-b2c-client-id'. I am trying to access this key in my code
using the @Value spring annotation.
e.g
@Value("azure.activedirectory.b2c.client-id")
private String activeDirectoryClientId;
The keyvault code replaces all the '.' characters with '-'
https://github.com/microsoft/azure-spring-boot/blob/master/azure-spring-boot/src/main/java/com/microsoft/azure/keyvault/spring/KeyVaultOperation.java#L117
so it can not transform it properly.
We've managed to find a workaround by having the following line in the application.properties
azure.activedirectory.b2c.client-id=${azure.activedirectory.b2c.clientId}
Any suggestions on how we should handle these kind of problems?
https://docs.microsoft.com/en-us/sql/connect/jdbc/using-always-encrypted-with-the-jdbc-driver?view=sql-server-ver15
- start Spring Boot app
- use spring-cloud-config client to connect to Config Server (which has a secure backend) and fetch the Azure Service Principal credentials (client ID and secret)
- use the Azure Keyvault Starter to fetch additional secrets from Azure Keyvault automatically (this one: https://github.com/microsoft/azure-spring-boot/tree/master/azure-spring-boot-starters/azure-keyvault-secrets-spring-boot-starter)
Hello, I'm an experienced Spring developer but an Azure beginner.
I succesfully used Azure Service Bus in a Spring Boot 2.2 backend. But I meet a problem when using Azure CosmosDB (I'm using the "com.microsoft.azure:azure-cosmosdb-spring-boot-starter:2.3.2" starter) :
- When using only Cosmos the app runs fine
- But when using Cosmos + a relational database (such as H2), the applications fails to start. It seems that the Cosmos lib wrongly finds and implements the JPA repository interfaces.
Does it ring a bell ? Is this the right place to talk about this issue ? Should I raise an issue in https://github.com/microsoft/spring-data-cosmosdb/issues ?
Thank you for your help. :)
