firebase / firebase/firebase-admin-java

Application Default Credentials take precedence over EmulatorCredentials

Aberta
#634 2 comentários 4 reações 1 responsável Reivindicada por @yuchenshi Ver no GitHub
api: firestore type: bug
Linguagem predominante
Java
Estrelas
620
Forks
305
Merge médio
3h 23min
PRs com merge (30d)
1

Descrição

### Environment
* Operating System version: Fedora 35
* Firebase SDK version: Firebase Admin Java
* Library version: 8.1.0
* Firebase Product: firestore

### Problem
If I have an Application Default Credentials File in `~/.config/gcloud/` than I get a warning about using user credentials for a server application while running my test against the emulator.
I do not expect to get this message as I am initializing the SDK with credentials provided and Javadoc for the Firestore Builder states that Application Defaults are only taken if Credentials are null.

#### Steps to reproduce:
Initialize the SDK in a Junit test like stated below.

Starting the test, the SDK will log the following message if there are Application Default Credentials:
`"WARN com.google.auth.oauth2.DefaultCredentialsProvider - Your application has authenticated using end user credentials from Google Cloud SDK. We recommend that most server applications use service accounts instead. If your application continues to use end user credentials from Cloud SDK, you might receive a "quota exceeded" or "API not enabled" error. For more information about service accounts, see https://cloud.google.com/docs/authentication/."`

Though, the test itself seems to run against the emulator just fine. Once I remove the Credentials by moving the credentials file, the test runs without warning.

#### Relevant Code:
```Kotlin
private val firestoreEmulator: Firestore by lazy {
FirestoreOptions.getDefaultInstance().toBuilder()
.setEmulatorHost(emulator.emulatorEndpoint)
.setCredentials(FirestoreOptions.EmulatorCredentials())
.setProjectId("demo-project")
.build().service
}
```

Guia de contribuição

Abrir o guia de contribuição

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.