Admin Console#
This document reviews the available options for configuring Casa. All configuration changes applied via the admin console take effect immediately with no restart or other actions required.
Enabled authentication methods#
Here you can choose the type of 2FA credentials you want to support in Casa. This may require you to enable the applicable interception scripts in your Janssen Server beforehand.
Check the boxes as desired. You can assign the handler plugin for each method to be supported. Choose "System" to use the default implementation provided by the application.
The "System" plugin supports several authentication methods out-of-the-box:
- OTP via SMS
- OTP (handles mobile apps and hard tokens)
- FIDO devices
- Super Gluu
In their home page, users will see widgets for every available method. These widgets are listed in decreasing order of ACR level. That is, the first method shown will be that with the highest level assigned in its corresponding interception script, and therefore the most secure.
Testing#
A recommended practice is to enable one script in the Janssen Server (like OTP), enable the associated method in Jans Casa, and then test and confirm that enrollment and authentication is working as expected. Then continue adding other methods one by one.
In an incognito browser, employ a user other than admin to test enrollments each time a new method is enabled.
This will prevent the admin user from being accidentally locked out.
Pass reset config#
An admin
can give users the ability to reset their password from inside Casa. To enable the password reset functionality,
navigate to Pass reset config and click the toggle to ON.
Reset to password authentication#
If a user is locked out for any reason (e.g. lost device, etc.), an admin can navigate
to Reset to password authentication in the admin console to turn 2FA off for them. Type the username (or part of) in
the text field and then press search. Once the user has been located, click the checkbox and click the
Reset to password button. The row will become disabled, and a success message will be displayed.
Branding#
Most organizations will want to custom brand Jans Casa. Follow our guide to learn more about custom branding Casa.
Plugins#
Through an easy-to-use screen, administrators can easily manage installed plugins and add new ones.
Logging#
Application logs are useful sources of information to diagnose anomalies and understand possible causes of errors if presented. Casa uses the Log4J2 logging framework for this. The severity level for logs can be modified at runtime and requires no restart. For more information about logging, check the FAQ entry.
CORS domains#
If a given plugin exposes one or more web services that are to be consumed from within a web browser, you can whitelist the origin domains from which consumption can takes place.
2FA settings#
Warning
This feature is only if the 2FA settings plugin is installed
In the 2FA settings screen, an admin can:
- Specify the minimum number of credentials a user must enroll before 2FA can be turned on
- Determine whether 2FA should be automatically enabled upon credential enrollment
- Whether users can turn 2FA on and off their own
- Whether users can choose a preferred authentication method
- Choose from a few predefined policies for when 2FA should be prompted.
To reduce the chance of lockouts, we recommend setting a minimum of two (2) strong credentials.
Predefined 2FA policy options include:
- Enforce strong authentication for every login attempt
- Prompt for 2FA when users' location is unrecognized
- Prompt for 2FA when users' device is unrecognized
- Allow the user to set their own strong authentication policy
The default policy is to enforce 2FA for every login attempt. If the admin opts to allow users to manager their own policy, a new widget will appear in the user-facing dashboard as described in the user guide.
In addition, the plugin exposes an API to programmatically manipulate these settings.
Created: 2023-10-05