loopback/lib/models
Ritchie Martori cc49d675ce Add Change model 2014-01-30 14:20:33 -08:00
..
README.md Update README for application model 2013-12-19 13:42:12 -08:00
access-context.js Add reference documentation using sdocs 2013-12-19 17:49:47 -08:00
access-token.js Remove the generated flag for access token id 2014-01-30 09:02:12 -08:00
acl.js Fix the Scope reference to models 2014-01-23 14:46:02 -08:00
application.js Make sure methods are called in the context of the calling class 2014-01-14 15:34:44 -08:00
change.js Add Change model 2014-01-30 14:20:33 -08:00
email.js Add reference documentation using sdocs 2013-12-19 17:49:47 -08:00
index.js Remove the dangling require 2014-01-16 09:12:52 -08:00
model.js Add loopback.compat to simplify upgrade to 1.6 2014-01-27 10:29:57 +01:00
oauth2.js Add oauth2 related models 2013-11-14 21:19:56 -08:00
role.js Fix the Role ref to RoleMapping 2014-01-23 15:04:48 -08:00
user.js Merge pull request #163 from strongloop/feature/include-user-in-login-result 2014-01-30 10:24:14 -08:00

README.md

Application

Application model represents the metadata for a client application that has its own identity and associated configuration with the LoopBack server.

Each application has the following basic properties:

  • id: Automatically generated id
  • name: Name of the application (required)
  • description: Description of the application (optional)
  • icon: URL of the icon
  • status: Status of the application, such as production/sandbox/disabled
  • created: Timestamp of the record being created
  • modified: Timestamp of the record being modified

An application has the following properties linking to users:

  • owner: The user id of the developer who registers the application
  • collaborators: A array of users ids who have permissions to work on this app

oAuth 2.0 settings

  • url: The application url
  • callbackUrls: An array of preregistered callback urls for oAuth 2.0
  • permissions: An array of oAuth 2.0 scopes that can be requested by the application

Security keys

The following keys are automatically generated by the application creation process. They can be reset upon request.

  • clientKey: Secret for mobile clients
  • javaScriptKey: Secret for JavaScript clients
  • restApiKey: Secret for REST APIs
  • windowsKey: Secret for Windows applications
  • masterKey: Secret for REST APIS. It bypasses model level permissions

Push notification settings

The application can be configured to support multiple methods of push notifications.

  • pushSettings

    pushSettings: { apns: { certData: config.apnsCertData, keyData: config.apnsKeyData, production: false, // Development mode pushOptions: { // Extra options can go here for APN }, feedbackOptions: { batchFeedback: true, interval: 300 } }, gcm: { serverApiKey: config.gcmServerApiKey } }

Authentication schemes

  • authenticationEnabled
  • anonymousAllowed
  • authenticationSchemes

Authentication scheme settings

  • scheme: Name of the authentication scheme, such as local, facebook, google, twitter, linkedin, github
  • credential: Scheme-specific credentials

APIs for Application model

In addition to the CRUD methods, the Application model also has the following apis:

Register a new application

You can register a new application by providing the owner user id, application name, and other properties in the options object.

Application.register('rfeng', 'MyApp1',
    {description: 'My first loopback application'},
    function (err, result) {
        var app = result;
    ...
});

Reset keys

You can reset keys for a given application by id.

Application.resetKeys(appId, function (err, result) {
    var app = result;
    ...
});

Authenticate by appId and key

You can authenticate an application by id and one of the keys. If successful, it calls back with the key name in the result argument. Otherwise, the keyName is null.

Application.authenticate(appId, clientKey, function (err, keyName) {
        assert.equal(keyName, 'clientKey');
        ...
});