[BUG] CosmoDB authentication failed despite connection string being correct

[mmaeffert]

Describe the bug
I am trying to connect the submodel repository to an external Cosmos Mongo DB in azure. Although the connection is successfull, it is throwing an authentication error:

com.mongodb.MongoCommandException: Command failed with error 18 (AuthenticationFailed): 'Invalid key' on server xx.global.mongocluster.cosmos.azure.com:10260. The full response is {"ok": 0.0, "errmsg": "Invalid key", "code": 18, "codeName": "AuthenticationFailed"}

To Reproduce
I try at least two configurations in application.properties:

basyx.backend = MongoDB
spring.data.mongodb.host=xy.global.mongocluster.cosmos.azure.com
spring.data.mongodb.port=10260
spring.data.mongodb.database=aas
spring.data.mongodb.authentication-database=admin
spring.data.mongodb.username=xy
spring.data.mongodb.password=xy

and

basyx.backend = MongoDB
sping.data.mongodb.uri = mongodb+srv://xx:[email protected]/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000
spring.data.mongodb.database=aas
spring.data.mongodb.authentication-database=admin

Both produce the exact same error.

BaSyx (please complete the following information):

• BaSyx submodel repository 2.0.0-SNAPSHOT
• BaSyx SDK Java

Additional context
I tried the connection string with other tools and it worked every single time, affirming that the credentials used are actually correct.

[aaronzi]

Hello @mmaeffert,

we will investigate what the cause of this could be.

It would be greatly appreciated if you could help us reproduce this. If possible, could you provide a docker-compose setup that you can share as a zip with us were we can directly see this issue happening? Testing against an external Azure is not an option for us.