You can create a profile that determines the authentication method and settings in
TeamForge.
You need to
have at least one user profile or more in active status before configuring the external
authentication.
-
Log on to the TeamForge as a site administrator
and go to the look project.
-
From the project navigation bar, click AUTH
MANAGER.
-
From the Main Menu pane on the left,
click Create Profile.
Fastpath: In the Manage Existing
Profiles page, if you do not find the desired one in the
list of existing authentication profiles, you can click New
Profile and proceed.
-
From the drop-down menu, select the type of the new authentication
profile.
-
Set the Jboss flag that determines the behaviour of the control flag with
multiple login-modules.
- Sufficient: The login-module is not required to
succeed. If it does succeed, control immediately returns to the
application (authentication does not proceed down the login-module
list). If it fails, authentication continues down the login-module
list.
- Optional: The login-module is not required to succeed.
If it succeeds or fails, authentication still continues to proceed down
the login-module list.
- Required: The login-module is required to succeed. If
it succeeds or fails, authentication still continues to proceed down the
login-module list.
-
Enter the value for each module
property
listed for the chosen profile type.
-
Click Create.
The confirmation message, The authentication profiles have been
imported. Activate the profiles to apply to TeamForge authentication, appears.
Remember: The newly created profile is
listed under
Authentication Profiles in the
Manage
Existing Profile page. It is now inactive and the status indicator
is yellow. You must
activate the newly created user profile.
Tip: Before you create any profiles using
Auth Manager, you may see an
inactive auto-imported
TeamForgeDatabase profile appearing under
Authentication Profiles. It is recommended to
delete the
Auto-imported UsernamePasswordInDatabaseLoginModule after
creating and activating your first profile. Because the subsequent login and
authentication request pass
only
through the active profile(s).