Skip to content

The fromStream method is deprecated. Please use the JWT constructor with a parsed stream instead. #6791

@leon

Description

@leon

Please make sure you have searched for information in the following guides.

A screenshot that you have tested with "Try this API".

This commit in google-auth-library is causing SecretManagerServiceClient to spit out console errors

https://github.com/googleapis/google-auth-library-nodejs/pull/2143/files

Solution

migrate away from fromStream and fromJSON to the newer implementations which also validates the input.

Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.

https://gist.github.com/leon/1ffa1b5ce77fad53ccdec8540cf77841

A step-by-step description of how to reproduce the issue, based on the linked reproduction.

Minimal reproduction

import { SecretManagerServiceClient } from '@google-cloud/secret-manager'

const secretClient = new SecretManagerServiceClient()
const secretResponse = await secretClient.accessSecretVersion({ name: 'projects/123123123123/secrets/my-secret/versions/latest' })

Will output

The `fromStream` method is deprecated. Please use the `JWT` constructor with a parsed stream instead. For more details, see https://cloud.google.com/docs/authentication/external/externally-sourced-credentials.

The `fromJSON` method is deprecated. Please use the `JWT` constructor instead. For more details, see https://cloud.google.com/docs/authentication/external/externally-sourced-credentials.

A clear and concise description of what the bug is, and what you expected to happen.

when calling the secrets apis we should not get console.warn messages

A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

The recent changes to the security holes in fromJSON, fromStream.

https://github.com/googleapis/google-auth-library-nodejs/pull/2143/files

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions