loopback/lib/models
crandmck cea2d30928 Merge branch 'master' of github.com:strongloop/loopback 2014-06-09 15:42:07 -07:00
..
README.md Update README for application model 2013-12-19 13:42:12 -08:00
access-context.js !fixup only set ctx.accessType when sharedMethod is available 2014-06-02 14:41:08 -07:00
access-token.js Make sure User/AccessToken relations are set up by default 2014-02-14 10:31:30 -08:00
acl.js JSDoc cleanup 2014-06-09 15:36:08 -07:00
application.js Remove the generated flag as the id is set by the before hook 2014-03-17 10:01:29 -07:00
data-model.js Fixup JSDocs; note: updateOrCreate function alias pulled out on separate line for docs 2014-06-06 17:17:37 -07:00
email.js Improvements to JSDoc comments 2014-03-14 10:28:31 -07:00
index.js Remove the dangling require 2014-01-16 09:12:52 -08:00
model.js !fixup only set ctx.accessType when sharedMethod is available 2014-06-02 14:41:08 -07:00
role.js !fixup only set ctx.accessType when sharedMethod is available 2014-06-02 14:41:08 -07:00
user.js Use constructor to reference the model class 2014-06-09 15:00:15 -07: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');
        ...
});