Skip to content

verifyCurrentUserAttribute should take metadata #8388

Open
@toschlog

Description

@toschlog

Is this related to a new or existing framework?

React

Is this related to a new or existing API?

Authentication

Is this related to another service?

No response

Describe the feature you'd like to request

When I call Auth.updateUserAttributes() I include clientMetadata that's used by my cognito-trigger code. This all works well.

When I need to re-request a code I call Auth.verifyCurrentUserAttribute(). This function, however, does take clientMetadata which is needed by my cognito-trigger code.

Describe the solution you'd like

Auth.verifyCurrentUserAttribute() should accept an optional clientMetadata object and pass that to the trigger function.

Describe alternatives you've considered

I'm probably going to have to have my trigger code save the metadata when called with updateUserAttributes() so it's available when called with Auth.verifyCurrentUserAttribute(),

Additional context

No response

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request
  • ⚠️ This feature might incur a breaking change

Metadata

Metadata

Assignees

No one assigned

    Labels

    AuthRelated to Auth components/categoryCognitoRelated to cognito issuesService TeamIssues asked to the Service Teamfeature-requestRequest a new feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions