Skip to content

Home

Development

IDEs

API Explorer

Releases

Release notes

Martini Runtime

Martini Desktop

Martini Online

Feature requests

Bug reports

Securing a Gloop API

By adding authentication to your Gloop APIs, you can limit their availability to certain users or groups. In order to add security to a certain Gloop API, be it SOAP or REST, follow the steps below:

Securing a Gloop API

Securing a Gloop API

  1. Open the Gloop API editor by double clicking on the target .api file from the Navigator view.
  2. Go to the Security tab of the editor.
  3. Choose your authentication scheme(s) by ticking any of the values under Authentication Type. The choices are:

    • None

      By default, your Gloop API has no authentication scheme set. This means that everybody can access your API and thus, you cannot specify a permitted Martini user or Martini group as that won't make much sense. If there are existing permitted Martini users or groups added to the API, the API will ignore them.

    • Basic

    • OAuth 2.0

    api.basic.auth must be set to true to make Basic authentication work

    The property api.basic.auth in your application .properties file should have a value of true or else, Basic authentication will not work. Changing this value during runtime will require an instance restart.

    1
    api.basic.auth=true
    
  4. Add a Martini user or group.

    When Basic, OAuth 2.0, or both authentication schemes are selected, you may add a Martini user or group by clicking the corresponding green, '+' button. Doing so would show either the Select User dialog or the Select Group dialog. From this dialog, you can proceed to selecting to whom the API is exposed to.

    Configuring users and groups

    To manage Martini users or groups, use the Users and Groups interface.

  5. Save the changes by clicking on the save button or by pressing .