Schritt 1: Wahl der Methode LDAP oder Database: Schritt 2: Database Settings Mapping Define attributes for username and password. Settings Choose a strategy to hash your password. The hash function transforms the password into a natural number (fingerprint). LDAP: LDAP as a standardized technique to get access to the authentication server. Common LDAP servers are: Apache Directory, Microsoft Active Directory, Open Directory, Oracle Internet Directory… Database: Uses a database table to store users and relevant information. The following fields are mandatory: USERNAME, PASSWORD

Letzter Schritt: Export der Angelegten Entities This wizard exports the created entities and attributes directly to your database. This can also be done manually by using the Project Management function 'Create tables form JPA entities‘ at any time.

oder oder Schritt 1: Wahl der Autorisierungsstrategie LDAP: The authorization will be executed by the LDAP server. In this case, the rights correspond directly to the rolls in the authentication server. Rights are represented by the groups and are directly assigned to the user. oder Database(JPA) Authentication is handled by the database. Following tables are required: USER, USERGROUPS/USERROLLES, PERMISSIONS/RESSOURCES. All three tables are connected to a ManyToMany (N/M) relation. This structure may be created automatically in the course of this wizard. If you already have an authentication based on LDAP it is necessary to create a new database table 'users' to be able to connect users and groups. Both elements 'user' and 'groups' has to be synchronized at runtime. LDAP: The authorization will be executed by the LDAP server. In this case, the rights correspond directly to the rolls in the authentication server. Rights are represented by the groups and are directly assigned to the user. oder Database(SQL) If you have a special structure to manage USERS, ROLES and PERMISSIONS in your database which is different to the recommended structure of RapidClipse, just define two simple queries which return the right result. 1. USER / ROLES: Define a statement which returns a result based on two columns: On the left side all users and on the right side the related role. Don´t use any groupBy statement. 2. ROLES / PERMISSION: Define a statement which returns a result based on two columns. On the left side all ROLES and on the right side the related PERMISSION. Don´t use any groupBy statement. It is possible to change the statements in the authorization provider class at all time.

Schritt 2: LDAP Konfiguration Schritt 2: Ressource Entity Mapping Choose the attribute which is for the resource name. HINWEIS: If you already have an authentication based on a USER table in your database it is necessary to keep the table synchronized with the LDAP server at runtime.

Schritt 2: Role Entity Schritt 2: User Entity Mapping Choose the attributs which contains the information about the user name and roles or create new attributs in existing entities, if they are not available. Mapping Choose the attributs which contains the information about the role name, resource and child roles or create new attributs in existing entities, if they are not available.

USER / ROLES: Define a statement which returns a result based on two columns: On the left side all users and on the right side the related role. Don´t use any groupBy statement. ROLES / PERMISSION: Define a statement which returns a result based on two columns: On the left side all ROLES and on the right side the related PERMISSION. Don´t use any groupBy statement. It is possible to change the statements in the authorization provider class at all time.