Autenticar usuarios - SDK .NET

Iniciar sesión

var user = await app.LogInAsync(Credentials.Anonymous());

var user = await app.LogInAsync(
    Credentials.EmailPassword("caleb@mongodb.com", "MySekritPwd"));

var user = await app.LogInAsync(Credentials.ApiKey(apiKey));

var user =
    await app.LogInAsync(Credentials.JWT(jwt_token));

var functionParameters = new
{
    username = "caleb",
    password = "MySekritPwd",
    IQ = 42,
    hasPets = true
};
var user =
    await app.LogInAsync(Credentials.Function(functionParameters));

var user =
    await app.LogInAsync(Credentials.Facebook(facebookToken));

var user =
    await app.LogInAsync(Credentials.Google(googleAuthCode, GoogleCredentialType.AuthCode));

var user =
    await app.LogInAsync(Credentials.Apple(appleToken));

Inicio de sesión sin conexión

Cuando tu aplicación Realm autentica a un usuario, almacena en caché las credenciales del usuario. Puedes comprobar si existen credenciales de usuario para omitir el flujo de inicio de sesión y acceder al usuario almacenado en caché. Usa esto para abrir un realm sin conexión.

The following example checks if there is a cached User object. If not, it logs the user in. Otherwise, it uses the cached credentials:

if (app.CurrentUser == null)
{
    // App must be online for user to authenticate
    user = await app.LogInAsync(
        Credentials.EmailPassword("caleb@mongodb.com", "MySekritPwd"));
    config = new PartitionSyncConfiguration("_part", user);
    realm = await Realm.GetInstanceAsync(config);
}
else
{
    // This works whether online or offline
    user = app.CurrentUser;
    config = new PartitionSyncConfiguration("_part", user);
    realm = Realm.GetInstance(config);
}

Log a User Out

Una vez que inicies sesión, puedes cerrar sesión llamando al método LogOutAsync():

await user.LogOutAsync();

Retrieve the Current User

Once you have an authenticated user, you can retrieve the User object with the App.CurrentUser property. The CurrentUser object is persisted in local storage, so even if the app shuts down after the initial authentication, you do not need to call LoginAsync again (unless the user logged out). Instead, use Realm.GetInstance(config), where config is a PartitionSyncConfiguration object. This approach results in a faster start-up and also enables the user to work offline.

// Returns a valid user access token to authenticate requests
public async Task<string> GetValidAccessToken(User user)
{
    // An already logged in user's access token might be stale. To
    // guarantee that the token is valid, refresh it.
    await user.RefreshCustomDataAsync();
    return user.AccessToken;
}

Expiración del token de actualización

Refresh tokens expire after a set period of time. When the refresh token expires, the access token can no longer be refreshed and the user must log in again.

If the refresh token expires after the realm is open, the device will not be able to sync until the user logs in again. Your sync error handler should implement logic that catches a token expired error when attempting to sync, then redirect users to a login flow.

For information on configuring refresh token expiration, refer to Manage User Sessions in the App Services documentation.

Observe Authentication Changes

Puede observar un flujo de eventos de cambio de autenticación llamando a User.Changed() en un objeto de usuario válido.

Actualmente, User.Changed() se activa en todos los eventos de usuario y debes agregar un controlador para garantizar que tus respuestas a los eventos sean idempotentes.

app.CurrentUser.Changed += (change, _) =>
{
    Debug.WriteLine($"Auth change: {change}, {_}");
};