When you use Atlas App Services to back your client app, you get access to a user object. You can use the .NET SDK to:
Create and delete users
Log users in and out
Create and update custom user data
Read user metadata from other login providers
For all authentication providers other than email/password authentication, App Services automatically creates a user object the first time a user authenticates. If a user authenticates via more than one method, you can link these user identities to a single user object.
You can delete user objects. Deleting a user object deletes metadata attached to the user object, but does not delete user-entered data from the backend or any custom user data. To delete custom user data, see Delete a User's Custom Data.
Apple Account Deletion Requirements
Apple requires that applications listed through its App Store must give any user who creates an account the option to delete the account. Whether you use an authentication method where you must manually register a user, such as email/password authentication, or one that that automatically creates a user, such as Sign-In with Apple, you must implement user account deletion by June 30, 2022.
Log users in with an existing third-party account, such as Apple, Facebook, or Google.
Create new user accounts with App Services email/password management, or your own custom function or custom JWT user management.
Enable anonymous users to let users access your App Services App without persisting user data.
When you have a logged-in user, SDK methods enable you to:
Open a synced realm with the user's configuration object
Run a backend function as the logged-in user
Change the active user in a multi-user application
Remove a user from the device
On successful login, the .NET SDK caches credentials on the device. You can bypass the login flow and access the cached user. Use this to open a realm or call a function upon subsequent app opens.
App Services manages sessions with access tokens and refresh tokens. Client SDKs supply the logic to manage tokens, and provide them with requests.
You can associate custom data with a user object,
such as a preferred language or local timezone, and read it from your client
application. A user object has a
customData property that you can use
to access custom user data.
To create and update custom user data, you must access your MongoDB data source directly. App Services does not offer a SDK method to create or update this custom user data; it's a read-only property.
Some authentication providers enable developers to access user metadata, such
as full name or email address. When you configure these metadata fields on
the App Services application, you can read this medata from your client app. A
user object has a
profile property that you can use to access