Tutorial: Mobile implicit login

var ref = new Webcom("<your-app>");
// Log in
ref.authWithWassup({mcc: "206"})
    .then(auth => console.log("Authentication succeeded", auth))
    .catch(error => {
        switch (error.code) {
           case "INVALID_PROVIDER_REQUEST":
             console.log("Your mobile network access could not be recognized.");
             break;
           case "PROVIDER_DISABLED":
             console.log("The implicit authentication method is disabled in the application. It must be enabled in the Webcom developer console.");
             break;
           default:
             console.log("An unexpected error occurs, please retry and contact your administrator.", error);
         }
    });

Unless you run a Javascript application on a mobile device, the Javascript API for implicit login should not be used directly.

Nevertheless, the authWithWassup function expects a JSON object as a first argument, with a mcc property that indicates the Mobile Country Code attached to the mobile device.

The auth parameter returned in the promise is a JSON object representing the signed in identity, which directly feeds the current authentication state. The following properties are specialized this way:

Property	Type	Description
provider	string	Equals "wassup".
providerUid	string	An immutable identifier of the authenticated mobile device. Note that this identifier is application-specific, so that the same user receives two distinct identifiers when authenticating from two distinct Webcom applications.

Webcom ref = new Webcom("<your-app>");
ref.authWithWassup(new OnAuth(){
  @Override
  public void onComplete(@Nullable AuthResponse authResponse) {
    // User account authenticated or logged-out
    String token = authResponse == null ? null : authResponse.getToken();
  }
  @Override
  public void onError(WebcomError error) {
    // User account not authenticated
  }
});

The authWithWassup method automatically retrieves the Mobile Country Code from the SIM card activated on the mobile device. Another signature of this method exists, which makes it possible to set an arbitrary MCC to perform the authentication (see the reference documentation).

In case of error, the onError method is called with an object describing the root cause of the error. Otherwise, the onComplete method is called with an authResponse object that either is null when the user has signed out or represents her/his identity when s/he has signed in.

Coming soon!
In the meanwhile, refer to the iOS API reference