¶ Authentication
After the SDK has been personalized, authentication processes can be performed. Similar to a personalization an authentication is primarily started by scanning a QR Code or handling an App-Link/Deep-Link. In addition, an authentication can also be initialized directly if the app acts as a service itself. This process is called InApp-Authentication. Normally, the app / SDK only functions as "key" in the authentication process. Meaning it has no knowledge of the user's data, for example the user's attributes (email address, name, birthdate etc.) or the MappingId used by the XignIn-Manager.
In the case of an InApp-Authentication the app can retrieve this data after a successful authentication. Furthermore, the authentication is also used in some utility process that need user confirmation which are referred in code as api access, e.g. changing the PIN or requesting a new activation. These processes also produce data with which an authentication process can be started directly from the app. For more information about how all these data can be acquired, please refer to the chapter Starting a process of the XignSys SDK.
The following diagram shows an overview of the authentication process, which is discussed in detail in this chapter.
¶ Chapter structure
The authentication chapter is structured and should optimally be worked through as follows: