Developers

Leverage the power of Asignio to secure your sites, apps, and services. And provide a security mechanism that actually makes your users happy.

Free Your Mind (& Time)

Development time and resources are precious. You want to focus on making your product into a killer app that everyone needs and wants. You don't want to spend that precious time reinventing authentication to outpace hackers, or incorporating some new arcane security standard. Let Asignio handle that for you.

Implementing Asignio is almost as easy as signing in with Asignio. As a developer, simply download and configure the Asignio plug-in for your sites, incorporate the Asignio control in your apps, and configure your services to talk to Asignio servers. All communication between your sites, apps, and services and Asignio is secure and you control when authentication takes place.

To request access to the Asignio Plug-in, Control, and API, please contact us. You will register for a developer account and obtain the keys necessary to offer the best authentication system available to your customers.

Integrate Asignio into your Web Application

Integrating Asignio into your web application is a simple process consisting of 3 steps:

  1. Contact us to request an Application Token for your web application and the URL for the Asignio Web Plug-in
  2. Initialize and configure the Asignio Javascript Plug-in
  3. Implement server code back-end verification with Asignio servers

Detailed instructions are below.

Request Application Token and Plug-in URL

Each application that utilizes Asignio is issued an Application Token to securely identify the application. This token is used in all secure communications between the web application and the Asignio servers.

As part of the application set up process, Asignio associates the action to be taken once authentication is complete. Developers tell Asignio which URL to call when Asignio authenticates a user. This call back tells the web application that the user has been authenticated.

Developers also need the URL to the Asignio Plug-in, which they will use to reference the plug-in javascript file into their web application. Once referenced, the plug-in can be initialized and configured.

Initialize and configure the Asignio Javascript Plug-in

Once the developer has referenced the Asignio Plug-in javascript file, they can initialize and configure the plug-in. This initialization should take place in a script block below the place where the Asignio plug-in javascript file is referenced. Asignio suggests that this take place at the bottom of the page.

Below is an example of plug-in initialization:

                    AsignioAuth.initialize({
                        applicationToken: "[Application Token]",
                        containerID: "[ID of div that contains the plug-in on the page]"
                    });
                

applicationToken: Without an active, authorized application token, any communication to the Asignio servers will be rejected.

containerID (optional): The Asignio plug-in renders some HTML elements into the DOM, including a sign in button that changes function based on the user's device (e.g., laptop/desktop vs. mobile). Developers can determine the location of the sign in controls by providing its container ID.

Once the AsignioAuth object is initialized (as shown above), the plug-in adds an Asignio sign in button to the DOM inside the indicated container. Users can sign in to a website on the laptop/desktop using the QR Code that appears when the Asignio sign in button is clicked. Users can sign in to the website from their mobile browser by tapping on the Asignio sign in button, which launches the Asignio application on their mobile device.

Once an authentication session begins, the Asignio plug-in listens for the Asignio server's response indicating that the user has been authenticated, and executes the call back indicated by the developers.

Add server code for Back-end Verification

Once the plug-in receives the response from the Asignio server confirming user authentication, it executes the call back URL that has been configured for this application. Developers need to add a server call to the Asignio servers to finalize authentication. This call is executed as part of the call back URL.

The server call to the Asignio retrieves the user token associated with the user on the developer's web application. This token is what connects the Asignio user to the developer's site user.

Developers need to add a single call via an HTTP request, and then handle the reponse that comes back from the Asignio server. The details of this call are provided to developers when they also receive their application token.