
Built-in and Extensible Security.
JasperServer uses the Spring sub-project, Acegi Security, for authentication and authorization. By default, user names and passwords are stored in the JasperSoft metadata repository and use form-based authentication. With the Acegi Security framework, you can instead plug into your existing security services without changing your environment or requiring extensive development effort.
Acegi supports all these technologies*:
Authentication Mechanism |
Notes |
|
An IEFT RFC-based standard |
|
An IEFT RFC-based standard |
|
An IEFT RFC-based standard |
|
A very common approach to cross-platform authentication needs, especially in large environments |
|
For simple user interface needs |
|
|
|
Otherwise known as CAS, which is a popular open source single sign on system |
|
HttpInvoker is a Spring remoting protocol |
|
Allows you to tick a box to avoid re-authentication for a predetermined period of time |
|
Allows every call to automatically assume a particular security identity |
|
Useful if one call should proceed with a different security identity |
|
|
|
So you can still use Container Manager Authentication if desired |
|
For legacy and other systems that don't follow any particular security standards. In this case, Acegi Security is an open platform and it is quite simple to write your own authentication mechanism |
* Source: Acegi Security Reference Documentation v.1.0.4
|
|