Need a lastLoginUpdate function.

[noah]

hi. @johnh @paul-winterhalder

I would like to request a function that allows for the forced update of a user's login time within the BrainCloud "User" tab.
Currently, the standard login function appears to be the only option, but I need to update the last login time via an S2S (Server-to-Server) call without actually performing the login process.

[noah]

I would like to update the information for this section via S2S.

[JasonL]

Could you share what you're using last-login time for (e.g. dormant-user cleanup, segments, promotions)? Last login drives several systems, including dormant-user identification and login analytics, so setting it without a real login would affect more than the display. If we know the goal, we can recommend (or consider) a more targeted option, such as tracking a separate activity timestamp or excluding those users from dormancy.

[noah]

We are developing our service using BrainCloud's S2S capabilities.
The client-side application does not include the BrainCloud SDK.

This is because we already have our own authentication system.
When creating users via S2S, we use the "External Auth Create" method and subsequently handle operations based on the profileId.

Therefore, to maintain a structure where existing user information is updated through the client's login process, the server must directly call the client authentication dispatcher API.

In the S2S setup, there is an issue where authentication calls can only be used to issue sessions via the s2sdispatcher. Consequently, the server is manually invoking authentication using the client-side API.

I consider this flow to be abnormal.

After all, even though the integration is S2S-based, the client login API still needs to be called once.

However, the issue is that without calling the client authentication, there is no way within the S2S setup to update the last login time and certain other information you mentioned.

I believe this is a common issue that can arise when adopting and using Brain Cloud within an existing system, much like in our case.

In summary, the user has created an external account in BrainCloud via the server using sysCreateUserExternalAuth.
We issue a token to the user based on our internal authentication system, signing it using the BrainCloudProfileId.
Consequently, authentication via the BrainCloud client is no longer required.
However, without client-side authentication, there is no mechanism to update information.
We need to find a solution to address this gap.