September 2006
Intermediate to advanced
562 pages
18h 33m
English
As Chapter 10 explains, security within the TUHRA application is based around several logical roles—user, admin, and manager. It is important to understand that these roles are private to the application and do not directly represent roles in the database or any user repository, such as OID. The reason for this approach is that it provides us with a security abstraction. We can hook up a security-provider implementation that has its own concept of roles, which may or may not match those within the TUHRA application. If the roles do not match directly, then a mapping can be made between the security-provider role name and the application role name once the application is installed into ...
Read now
Unlock full access