Welcome to the Trustbind developer documentation.Trustbind is a user authentication service which completely replaces the typical password-based authentication which is normally used when accessing online services, so removes your largest cyber-security risk, and streamlines your user experience to increase customer satisfaction.
All your customers need to do to access your website/application is to click the login button and use our simple PIN interface (the 'M-Pad') to authenticate themselves:
Here you will find all you need to integrate the Trustbind secure login system into your own website/application and deliver the highest level of security for users logging in to your services.
What you will learn in this documentation is how to use any of our SDKs to present your users with the login button, initiate the Authorization Flow to obtain an access token for an end-user and present this to the authentication platform to initiate final validation and login via simple PIN with the 'M-Pad' (loaded from the mpad.js library).
The first step to take is to follow the instructions found in 'Register / Create a new app'.
Once you have created a new app in your portal and obtained the necessary credentials, you should read through 'Authorization Flow Explained' to get an understanding of the generic configuration and user authentication process, as applies to all of the SDKs.
The 'Intro to the Login Button' section will then give you an overview of how the login button is added to the front end of your website, as the initiator of the authentication process.
The 'SDK Instructions' section then gives full, language-specific instructions on configuring the login button and managing the authentication process. This section will expand on what you have learned in 'Authorization Flow Explained' and appropriate it to the language of each SDK. Here you will find the basic SDK installation process with sample apps for each SDK, and a breakdown of the code involved in creating apps.
Developer note: For developers wishing to implement their own OIDC code without the assistance of our SDKs, the issuerURL is
Finally, there is a Portal Guide, which gives instructions on how to make use of the Trustbind authentication portal dashboard to manage your apps, as well as access statistical overviews and reports.Top