Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tutorial for OIDC Activation #46

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file not shown.
66 changes: 66 additions & 0 deletions docs/tutorials/OIDC-Based-Activation/Readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
# OIDC Based Activation

<!-- AUTHOR marekstransky 2024-12-16T00:00:00Z -->
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that there can be only a single author 😉

<!-- SIDEBAR _Sidebar.md sticky -->
<!-- TEMPLATE tutorial -->
<!-- COVER_IMAGE ThirdParty_OIDC_Login.webp -->

OpenID Connect ([OIDC](https://openid.net/developers/how-connect-works/)) has become a leading interoperable authentication protocol built on [OAuth 2.0](https://oauth.net/2/), the industry-standard protocol for authorization.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whole introduction test is mainly copy&paste from the post from Grace https://www.wultra.com/blog/wultra-now-supports-oidc----heres-what-it-means-for-secure-identity-verification

OIDC offers tangible benefits for banks, fintech companies, and users alike — to highlight its potential to transform secure identity identification, let’s explore how OIDC works and how our solution is expanding its real-world applications.


## Introduction

OIDC enables third-party applications to verify an end user’s identity and gather basic profile information through trusted third-party providers.
You’ve likely encountered this protocol when logging into one of many services that use Google, LinkedIn, or Facebook accounts.

While social accounts and emails are common in general verification, these methods aren’t robust enough for businesses in the financial sector that require top-tier security.
It’s for this reason that banks and fintech companies turn to more secure methods — like digital bank IDs — that prove a user’s identity while also ensuring full compliance with regulatory standards.

For example, banking customers in the Czech Republic can now verify their identity via OIDC using [Bank iD](https://bankid.cz/).
Similar capabilities extend across Europe, as a growing number of national bank IDs support OIDC, including Finland’s Bank ID (part of the [Finnish Trust Network](https://www.signicat.com/use-cases/finnish-trust-network)), Belgium’s [itsme®](https://www.itsme-id.com/en-BE), Norway’s [BankID](https://bankid.no/en), Denmark’s [MitID](https://www.mitid.dk/en-gb/), and the Netherlands' [eHerkenning](https://www.eherkenning.nl/en), among others.


## Mobile Token

We offer several methods for activating our standalone mobile token app.
Now our mobile token incorporates OIDC feature via standardized API.
This additional functionality allows users to verify their identity through third-party methods (Web Login).
Activating our mobile token via Web Login is simple.

![](./Image_OIDC_Steps_To_Auth.webp)

It’s important to note that this is an example of the process, as the instructions will differ based on a user’s digital bank ID.


## Real-World Examples of OIDC in Action

There are a number of important use cases in which Wultra’s OIDC-based authentication can be put to use:

- **Forgotten credentials:** If a user forgets their password or login details, they can use OIDC (through a verified third-party account) to regain access.
- **New device activation:** When a user gets a new phone, they can seamlessly transfer the mobile token, which prevents any disruptions to their access.
- **Digital bank IDs:** As mentioned above, our integration enables users to verify themselves via the array of European digital bank IDs that support OIDC.


## Benefits of Using OIDC

In a nutshell, OIDC enhances user experience, supports broad compatibility for easy scalability, and enables banks to meet compliance standards through eKYC.

- **Positive user experience:** The ability to log in with a familiar third-party service makes accessing one’s accounts quicker and easier, reducing login fatigue and enhancing user satisfaction. Minimizing steps results in faster registration, fewer abandoned accounts, and increased engagement.‍
- **Standardization and interoperability:** OIDC is an open standard, which makes it both widely compatible with various platforms and services and easy to implement. Banks and fintech companies can easily scale and adapt authentication systems during various stages of growth.‍
- **Identity assurance support (eKYC):** Through OIDC, banks can implement electronic Know Your Customer (eKYC) processes. This ensures regulatory compliance and aligns with industry standards for identity assurance.


## SDK

TODO marek


## Backend

TODO Lubos


## Summary

In this tutorial we have shown how to use the OIDC protocol together with mobile token, which leverage activation that’s both secure and user-friendly.
Binary file not shown.
17 changes: 17 additions & 0 deletions docs/tutorials/OIDC-Based-Activation/_Sidebar.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
**Table of Contents**

[Home](Readme.md#)

[Introduction](Readme.md#introduction)

[Mobile Token](Readme.md#mobile-token)

[Real-World Examples of OIDC in Action](Readme.md#real-world-examples-of-oidc-in-action)

[Benefits of Using OIDC](Readme.md#benefits-of-using-oidc)

[SDK](Readme.md#sdk)

[Backend](Readme.md#backend)

[Summary](Readme.md#summary)