Related links
Homepage
User documentation
Uživatelská dokumentaceFramework Core functionality
- AyMINE Framework Server
- Configuration of the user-defined fields
- Client-Defined attributes
- Default server methods
- Strings and translations
- User sessions
- Import collection of objects
- Multi tenant Architecture
- The AyMINE licence model
- Export collection of objects
- System messaging
- System Rights
- File Management with End-to-End Encryption
- Server configuration for large files
SOA / Event Management
Support for Service Object Architecture and Internal Event ManagementModule - support for management
Front-End Scripting
System Management
- SaaS Management Module
- Management of the SaaS service client
- Encryted wallet storing access keys for data vault
- Definition and Management users in the SaaS system
- Management of the system users
- System right management
- System role is how user administrator sets the rights
- File access, storing and locking
- Communication geateways
- Private Object Marks, Sign & Notes
Task Management Module
- About TSK module
- Support for voting and decision management
- Support and implementation notes for FMEA
- Support for the Methodology Management
- Project Methodology Support
- Project Roles - Data model and implementation notes
- Actions and Meeting Agenda
- Description of person and supplier competencies
- Business event
- Problem & Helpdesk management support
- TSK module releases
- User Reminder
Task & Task pattern
Mobile & Web Application
- Client-Side Scripting using API
- Application Object Structure
- Clipborad Link - Cliplink
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- Object API – object <g>
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
CMS - Content Management & Web API services
FI - Finance Management
CRM - Customer-Relationship Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partTwo-factor login
Two-factor login supports verification of the login using fingerprint mobile confirmation, email or SMS confirmation
- The registration of a device for 2. factor
- Login using the 2 factor
- Login to the trusted device
- Confirmation using SMS
Two factor authentication primarily expects authentication using the fingerprint confirmation through the mobile application. The email confirmation is used to set up the mobile application and confirm the trusted device.
Two factor security is on the security level used by banking applications and on the level required by standards like ISO 27000 or TISAX.
The registration of a device for 2. factor
Activity scheme describes, how to set up mobile device as a trusted devices for 2-factor authentication
Registered device currently shall used Android. iOS devices are under testing.
Login using the 2 factor
The following activity scheme describes login process to the browser–based application with 2 factors:
Login to the trusted device
User can set up a device as a trusted device. When a computer and browser is set up as a trusted, it allows login without second device confirmation.
Mobile devices confirmed to be a trusted device supports login using bio-metric authentication without confirmation by another factor.
Confirmation using SMS
SMS confirmation is allowed as an add-on service for business client with the application payment scheme.