api.user.setAppMetadata does not work in post login action

[ThomasFisher]

We have a scenario where certain users with a certain connection type may log in with missing App_Metadata. To remedy this, we have a post-login action that

1. checks if (connectionTypeMatches && isMissingMetadata)
2. queries an endpoint - let newData = await axios.post(‘getMissingDataEndpoint’, data, options)
3. sets App_Metadata from newData
4. updates profile claims on idToken and accessToken

The first problem I am running into is in step 3, calling api.user.setAppMetadata(({ id: event.user_id }, { profile: newProfile }); does not update the user’s app_metadata.

I found this post:

Set User Metadata Is Not Working Inside Post Login Action

Hi, this is Yasin. Problem This is for social login providers. I am trying to set the user metadata and read it after setting it, in a single post login action file. However, I get an error. Either the user metadata cannot set on Step 5 or the newly set user metadata cannot be read in Step 6 because I get an error This is a fundamental issue and I have to solve it as quickly as possible. Thank you so much! Post Login Action - Code Flow (Please read) Code flow is like this: Check if t…

and decided to comment out the updates to the idToken and accessToken to prep for potentially moving that logic into a new action. However, when I run the action in debug mode with a custom event pointed to a test account, the action completes successfully, but the test account does not get the expected metadata updates. I have logged the new data, confirmed everything is being queried correctly, and that the new data is being built as expected. I even see in the Test Results pane a Commands array with a SetMetadata command in it, and the command seems to have the relevant correct data. When I refresh the user’s detail page after running it though, the updates are not present on the profile.

This link mentions it should be possible to add the management api as a dependency to the action and update it that way:

Different Strategies to Update User Metadata in Post-Login Action

Problem statement In Post-Login Actions it’s possible to save user metadata with the following methods: api.user.setAppMetadata(name, value) api.user.setUserMetadata(name, value) However, it’s also possible to instantiate the ManagementClient in an Action to save user metadata. Are there any tradeoffs to choosing one method over the other? Solution In the case of updating user metadata, the primary difference is that the ‘API’ method surfaced by the Action will aggregate calls to update a use…

However, when I try that, I get a “management.updateAppMetadata is not a function”

[ThomasFisher]

The best I could tell was happening here is that the action did not like waiting for a response from the endpoint. Ended up just reworking the endpoint being hit to include the extra management-api logic.

• This is not ideal, as it makes it impossible to put the profile updates on the issued token. We had to solve this through more hacks w/ silent authentication.