A security realm defines the mechanism for user authentication and authorization. FlexDeploy provides a default internal realm for users, which is based on FlexDeploy database tables for Users and Groups. FlexDeploy also supports Active Directory and other LDAP based realms for authentication and authorization using an external directory server. You can define multiple security realms. To configure/view the realms, select Administration -> Security -> Realms from the menu. FlexDeploy has out of box realm which can be utilized as well along with external directory servers.
Realms can be ordered to ensure that authentication checks are done in particular order. If you define multiple realms, users are authenticated against each realm in specified order until the first successful authentication occurs. Authentication will stop when first successful authentication against any realm in list (bug was identified here where authentication continued through all realms, bug fixed with 5.2.0.1).
If Group Mapping is enabled for realm where authentication is successful, Groups are derived from mapping configured for that realm. Groups assigned in the FlexDeploy internal realm are always used as well, so if you wanted to provide additional groups to users defined in external realm, you can do that in FlexDeploy - Users screen. Group mapping in the Realm is optional, in which case you must assign Groups to Users using FlexDeploy – Users screen.
FlexDeploy internal realm (fdRealm) can also be adjusted in list of realms. This feature was enabled as part of 5.2.0.1, previously internal realm was added at the end of realm list. FlexDeploy 5.4.0.1 allows customer to adjust internal realm order (possibly first), which would allow login with local user when external directory servers are having issues. For example, if directory servers are having performance issues, login with local user may take long time, but if you adjust internal realm to be first in the list, then you will notice faster login for local users in that situation.
External realm users will have their passwords managed in the external realm, not in FlexDeploy.
New User Process
A user record must exist in FlexDeploy even for External Realm Users. This is necessary so that user can control Notification settings and allows the FD Administrator to provide additional Security if necessary.
When users defined in an External Realm log in successfully for the first time, a new User record is created in FlexDeploy. At this point, the user is asked to provide various information like First Name, Last Name, Email etc. The password for such users is always managed by the External Server. Once the user provides the necessary details, an automatic logout will occur and the user will have to login one more time. At this point, user will be granted access based on Realm Group Mapping configured by the Administrator, which is explained later in this document.
Create LDAP Realm
To create an LDAP Realm click the Create button and Select LDAP Realm.
Any changes to LDAP Realm's Configuration tab will require the FlexDeploy application server to be restarted. You can test realm configuration details by clicking on the Test button.
WebLogic Embedded LDAP Realm Example
Apache Directory Server Realm Example
Enter the details for the LDAP realm as described in table of inputs below. Click the Save button to save the changes.
Use the Move Up and Move Down buttons to change the order of the Realms.
Use the Active check box to activate or inactivate a specific Realm. You can use the Delete button to completely remove a specific Realm from FlexDeploy configurations.
All LDAP Realm users must be under specific branch on the LDAP server, which is searched by User Search Base and User Search Filter in configuration details.
FlexDeploy uses memberOf virtual attribute to derive User's groups, so if your LDAP does not support that attribute, group mapping will not work.
Field | Required | Description |
|---|---|---|
Realm Name | Yes | Name of the LDAP Realm. |
Description | No | Description of the realm. |
Active | Yes | Whether the realm is active or not. Default is Active. |
User Search Base | Yes | Provide User base tree in LDAP server. For example, ou=users,ou=system. |
User Search Filter | Yes | Provide User search filter to find user records in User Search Base. For example, (&(objectClass=*)(uid={0})) |
URL | Yes | Provide URL to access LDAP server. For example, ldap://localhost:10389 |
System User Name | Yes | Provide read-only user name to access LDAP server. For example, uid=admin,ou=system |
System Password | Yes | Provide password for specified system user name. |
Group Mapping Enabled | No | Check if you want to map LDAP groups to FlexDeploy groups. LDAP server must support memberOf attribute for group mapping in FlexDeploy. |
Group Search Base | No | Provide Group base tree in LDAP server. For example, ou=groups,ou=system. |
Group Search Filter | No | Provide search filter to find groups in Group Search Base. For example, (objectClass=groupOfUniqueNames) |
Create Active Directory Realm
To create an Active Directory Realm, click on the Create button and Select Active Directory Realm.
Any changes to Active Directory Realm's Configuration tab will require the FlexDeploy application server to be restarted. You can test your realm configuration details by clicking on the Test button.
Enter the details for the Active Directory realm using the details in the table below. Click the Save button to save the changes.
Use the Move Up and Move Down buttons to change the order of the Realms.
Use the Active check box to activate or inactivate a specific Realm. You can use the Delete button to completely remove a specific Realm from FlexDeploy configurations.
All Active Directory Realm users must be under a specific branch on Active Directory server, which is searched by User Search Base and User Search Filter in configuration details.
An Active Directory Realm can be used for authentication as well as authorization using the Group mapping feature.
Field | Required | Description |
|---|---|---|
Realm Name | Yes | Name of the Active Directory realm. |
Description | No | Description of the realm. |
Active | No | Whether the realm is active or not. Default is Active. |
User Search Base | Yes | Provide the user base dn in the Active Directory server. For example, CN=Users,DC=flexagondev,DC=local. |
User Search Filter | Yes | Provide the user search filter. For example, (&(objectClass=*)(sAMAccountName={0})) |
URL | Yes | Provide URL to access active directory server. For example, ldap://localhost:10389 |
System User Name | Yes | Provide read-only user name to access active directory server. For example, CN=flexservice,CN=Users,DC=flexagondev,DC=local |
System Password | Yes | Provide password for specified system user name. |
Group Mapping Enabled | No | Check if you want to map active directory groups to FlexDeploy groups. |
Group Search Base | No | Provide Group base tree in active directory server. For example, CN=Groups,DC=flexagondev,DC=local . |
Group Search Filter | No | Provide search filter to find groups in Group Search Base. For example, (objectClass=group) |
Group Mapping with External Directory Server
FlexDeploy provides features to map external directory server groups to FlexDeploy groups, which makes it very easy to manage FlexDeploy users in your environment. Fine-grained access to FlexDeploy features is still controlled by FlexDeploy groups, and by mapping external directory groups to FlexDeploy groups, you essentially control access to FlexDeploy features. You can configure FlexDeploy group permissions using the Groups screen and Security tab on each Application/Folder/Project tab on the project tree structure.
In order to setup Group mapping, check the Group Mapping Enabled checkbox on the Configuration tab. Then select the Group Mapping tab. Select a specific FlexDeploy group to work with first. Then shuttle desired External groups to Map the, to FlexDeploy Groups. See the figure below, where we have mapped the Active Directory Groups Administrators and Enterprise Administrators to the FD Administrators group.
Realm configuration changes require a recycle of the FlexDeploy server process, including the mapping configuration, but changes on the Group Mapping tab do not require a recycle.
