-
Notifications
You must be signed in to change notification settings - Fork 1
Home
This document remains the intellectual property of Monet +, a.s. Information contained in this document are subject to business secrets pursuant to § 17 of Act No. 513/1991 Coll. as amended. Duplication and / or transmission of any part of this document to a third party is not allowed without the prior written consent of the authors. Authors of the document agree to use the information listed in this document for the purposes specified in the title of the document.
CASE is solution from Monet+ that is used for client authentication and authorization of some operations. Whole solution is fairly complex and full description is out of scope of this document. However, CASE is supporting multiple methods of authentication and authorization. One of them is called CASE mobile. Essentially it is an application for mobile phones.
Only basic concepts used in CASE mobile applications are explained here. All CASE mobile applications have some common functionality. CASE mobile SDK is library that is encapsulating these common features. This document describes how to utilize them to programmers advantage. After reading this document, reader should be able to use CM SDK and build his own CASE mobile application.
| Term | Description |
|---|---|
| SDK | Software Development Kit, library |
| CM | CASE mobile |
| CM SDK | CASE mobile SDK |
| OS | operating system (etc. Android, iOS) |
Life of any CASE mobile application has two stages. After installation, it starts with no data and its functionality is limited. User has to pair it with his/her identity. This enrollment process is called activation. After successful activation CM is in activated state and can be used for authentication or authorization.
In fact, CASE mobile SDK is not one library. To provide more flexibility, it is decoupled to multiple modules (or libraries) with various dependencies.
There is no need to distinguish between modules in this documentation. Applications rarely use classes or methods, that are not from API of CM SDK. Therefore, we refer to CASE mobile SDK as if it was one library.
Talsec Certificates is an SDK for managing endpoint service certificates on Android and iOS. It emphasizes certificate pinning to protect against attacks like Man in the Middle and DNS spoofing. Traditional methods require app updates for certificate changes, but TalsecCertificates offers dynamic endpoint certificate updates, enhancing practicality.
Talsec Certificates documentation: Talsec Certificates. Integration to application is described in chapter 3.
In Initialization and config#initialization is described how are TalsecCertificates instances paired with Account & AccountType in CM SDK.
Following subsections will explain ideas behind different parts and concepts of CM SDK. Only general principles are explained here. Low level information (like description of method inputs and outputs) are out of scope of this documentation. For details check corresponding javadoc and swiftdoc.
Documentation also contains code snippets to show usage of particular methods, classes or groups of classes on Android, iOS or both platforms.
Following concepts are described: