Access to Casa github repo is required to go through developer doc pages. Please request read access to the repository before undertaking any development task.
What are plugins?#
A plugin is an artifact packaged in a Java ARchive (jar file) that augments the functionalities available in your default Gluu Casa installation. Under certain circumstances, plugins can override existing application functionalities.
Plugins are mostly written in the Java programming language, but Kotlin can also be used.
What can you do with plugins?#
Plugins are very versatile, the following is by no means an extensive list of things you can do via plugins:
- Add menu items in user's menu, top-right dropdown menu, or admin's dashboard menu
- Add UI pages with arbitrary content (and backend-functionality!), this also applies for the admin dashboard
- Add RESTEasy services
- Add or override authentication mechanisms to be supported by the application
In addition to the above:
- Any plugin can have easy access to the underlying LDAP of the Gluu Server where casa was installed
- Plugins can onboard their own libraries (jar files) and classes
What can't you do?#
- Remove, deactivate or alter existing menu items found in your default installation or added by other plugins
- Alter the way in which certain features look or work such as: password reset, default admin dashboard functionalities, logout, etc.
- Plug custom logic to intercept calls or listen events when they occur (e.g. trigger a notification when a user has enrolled a specific type of credential)
- Alter the authentication flow. While this is not feasible via plugins, you can customize the flow by editing the Casa interception script and its associated custom pages bundled with your Gluu Server installation
- Use Dependency Injection
- Use Enterprise Beans (EJB)
- Adding/overriding authentication mechanisms
- Tips for plugin development
- Internals of plugin management in Casa
APIs for credential enrollment#
Despite Casa having enrollment capabilities built-in, a use case may arise where credential enrollment needs to happen elsewhere in your app ecosystem. A typical scenario is in a user registration application, where users are asked to enroll strong authentication credentials during account creation.
For this, developers have access to a REST API which faciliates the credential enrollment process. Currently, the following types of credentials can be enrolled using the API:
- OTP by SMS
- TOTP or HOTP mobile applications (like Google Authenticator)
- Super Gluu push authentication
- FIDO 2 security keys
Per spec FIDO 2 credentials can only be enrolled from a page belonging to the same domain or subdomain of your Gluu Server.
The Swagger definition document is located at
https://<host>/casa/enrollment-api.yaml. You can leverage swagger-codegen to bootstrap the process of creating a client application in order to consume the service in a variety of programming languages. You can achieve similar effects by using Swagger Hub.
Additionally, the Casa sample plugins repo contains a small client-side application that mimicks the process of enrolling credentials in Casa using the REST API. If you ever had trouble with it, please open a support ticket.
As the Swagger yaml document states, the API is protected by a bearer token. That is, developers have to pass a suitable value in the authorization header for requests. This means an OpenID Connect client must be previously registered in the underlying Gluu Server in order to interact with the server's token endpoint.
For more information about crendential enrollment via APIs, visit the developer FAQs.