How to integrate UbID into a Web application

1. General Information

1.1 What is an Unbreakable Identity?

The self-managed digital identity guarantees a solid, reliable, legitimate, secure digital identity that is not subject to unauthorized modifications. It has a user profile associated with it in a secure and efficient way. It can integrate a strong proof of identity to verify the identity of the applicant. Provides a secure process to authenticate users in applications. The authenticated user delegates security and permissions to the client application easily.

1.2 Benefits of the Unbreakable Identity technology

Unbreakable Identity (UbID) thanks to digital identity provider UbID.app facilitates enrollment and proof of identity, as well as recurring digital authentication, to easily integrate with software applications using the OpenID Connect standard, with many other advantages and benefits.

The administrator user is required to have created an application to integrate within the environment that UbID provides, as seen below there are two applications created by the administrator user.

2. How to integrate UbID into a Web application

The administrator user is required to have created an application to integrate within the environment that UbID provides, as seen below there are two applications created by the administrator user.

2.1 Integration

To start the integration you must select the “Keys” button in the application:

If you have not yet generated a connection key, you must go to the “Generate new key” button so that the system assigns you an integration key. Follow the steps that the system presents to you (you can also consult the step-by-step guide where this process is detailed).

Once the system has generated the key, you will see a screen like the one below.

Afterwards, you have to program and incorporate the link that is seen in the part that says “the button that you implement in your application and that accesses IDP must contain the following”. In this example case we have:

In the link you can see 3 parts (the keys that you see below are an example, you will see your own keys:

1. The domain: https://idp.ubid.app
2. The project (realm): ?realm:ubid.app
3. The application (client): ?client:c3da6d80-ce67-48a9-9a90-4eb5cd87eaf0

Additionally, we can add the option: ?session

The session (a unique ID that identifies the session): A UUID that identifies the transaction and that must be incorporated in the URI, as shown below. This is optional, but it is suggested to incorporate it so that through the APIs provided by UbID, you can obtain the user data and the token of the person who has logged in.

You can also preview the login, getting an example of how it works, by pressing the “Preview” button:

The template that UbID suggests is a modern and minimalist template, as shown below, the wallpaper is changed in the “Wallpaper” option. The wallpaper shown is just an example.

On the login screen you can see the following:

1. Project name (example: Ubid.app, or the name of your company).
2. Application name (example: Miamicity.app, or the name of your application).
3. Two buttons: “Create new account” and, “Use an existing account”.

When the user connects via UbID to your application, the system will provide a connection token.

This token and the username of the connected user can be captured with the sessiondata API. (It requires as a condition that the ?session option has been incorporated in the URL in the link detailed above)

In addition, the basic data of the connected user can be captured: Names, surnames, email, phone, etc… with the userdata API. (It requires as a condition that the ?session option has been incorporated in the URL in the link detailed above)

The APIs must contain the authorization key in the header. This key can be obtained in the “Keys” option, “Private key” option.

The APIs and their implementation are detailed in the APIs tab, as you can see below: