Create Directory & Service

Create a Directory

Directories belong to your organization and are linked to specific Authenticator SDKs. A directory can contain one or more services, and each of these services will interact with the same Authenticator SDK within your mobile app. This means you can have one service for logins and another for purchase authorizations, and both will be authorized by your Users through the same Authenticator SDK within your mobile app. To create a directory:

  1. Log into Admin Center and navigate to the Organizations landing page, and then click on the name of the organization you created previously.
  2. Scroll down to the directory section and click the Create directory button.
  3. Fill in the form with a name for your directory; this won’t be public, so make it something descriptive that means something to you such as “ Group”, etc.
  4. After submitting the form, you will be taken to the Details page for that directory. Take note of the SDK Key as you will need this later when integrating the Authenticator SDK in your Mobile App. Remain on the details page and move on to the next step.


What is a Service?

An service is the central component of the LaunchKey Platform that allows you to manage the way your Service, Mobile App, and Users interact with the Platform API. an service is used used by developers and managed by administrators from within Admin Center.

Create an Authenticator Service

Now that you have a directory, create an authenticator service from within that group:

  1. Navigate to the Services section and click the New Service button.
  2. Choose a name, description (optional), and avatar (optional) for your Service — these will be displayed to the end user during Auth Requests.
  3. Read and agree to the Developer Terms of Service and click the Create Servic button to proceed.
  4. After the form has been submitted, you will be taken to the Details page for the Service you just created. Move on to the next step.

Configure Service Keys

The Service Details page for your LaunchKey Service is where you’ll manage how your Service, Authenticator SDK, and Users interact with each other through the Platform API. The page contains three tabs: General, Keys, and Security. Navigate to the Keys tab to configure your service’s encryption keys:

  1. Create a new Secret Key by clicking New Secret Key and select either Download New Key or View & Copy New Key. Securely take note of this new secret key for use later, but never share this key with anyone!!
  2. Create a new Public Key by doing one of the following:
    • Upload an RSA public key file from a public/private key pair you generated yourself by clicking New Public Key and selecting the Upload New Key option.
    • Allow Admin Center to generate a new RSA public/private key pair for you by clicking the New Private Key button and select either Download New Key or View & Copy New Key. As with your Secret Key, securely take note of the keys and do not share them with anyone. The Private Key will be used to decrypt and verify signatures for data you receive from the LaunchKey Platform API.
  3. Finally, take note of your service Key and authenticator SDK Key which will be used by your Service and Authenticator SDK respectively.

Security Settings - Optional

The following security options found within the Security tab can be configured to enforce various security policies for your Directory Users through the Platform API. Modify these settings as you see fit based on the security needs of your service.

Security Fencing:

Restrict authorizations by ensuring end users and their mobile devices fall within certain bounds (rules) such as:

Geofencing:Restrict authorizations to one or more geographic zones
Time-Fencing:Restrict authorizations to one or more time frames

Restrict authorizations to specific users you specify within this whitelist

Force Auth Factors:

Your users can choose to use various authentication factors through the Authenticator SDK, or your service can force them to use authentication factors, such as:

Type:Force users to use one or more types of authentication factors (i.e. inherence, possession, and knowledge)
Amount:Force users to use a certain amount of authentication factors (i.e. to ensure they’re using multi-factor authentication)

User Contributed

LaunchKey links to user contributed code as a resource to its community. LaunchKey does not in any way guarantee or warrant the quality and security of these code bases. User contributed code is supported by the creators. If you do find a link from the site to user contributed code that is malicious or inappropriate in any way, please report that link to LaunchKey immediately and we will investigate the claim. Submit any issue to LaunchKey support at ×