Group items matching

in title, tags, annotations or url

Just bit of a warning when using this, there was a bug in 7.1.1 when you added mime type that prevented server to start.so please use 7.1.2 or 7.2 nightly builds where this is fixed.

simplified and unofficial UML Profile for EJB 3.0 with support for

Enterprise JavaBeans

session beans

-Dorg.granite.logger.impl=path.to.my.CustomLogger

other CDI Extensions projects.

container agnostic

different containers get activated via

CDI container integration via

Building Apache DeltaSpike

DeltaSpike-0.3

Release Notes

[DELTASPIKE-62] - Discuss security module

[DELTASPIKE-74] - unit and integration tests for @Secured

 [DELTASPIKE-75] - documentation for @Secured

[DELTASPIKE-78] - review and discuss Authentication API

 [DELTASPIKE-77] - review and discuss Identity API

[DELTASPIKE-79] - review and discuss Authorization API

[DELTASPIKE-81] - review and discuss Identity Management

[DELTASPIKE-82] - review and discuss external authentication

[DELTASPIKE-176] - unit and integration tests for @Transactional

[DELTASPIKE-177] - documentation for @Transactional

 [DELTASPIKE-179] - unit and integration tests for @TransactionScoped

[DELTASPIKE-175] - @Transactional for EntityTransaction

 [DELTASPIKE-178] - @TransactionScoped

 [DELTASPIKE-190] - Create ConfigurableDataSource

[DELTASPIKE-219] - @Transactional for JTA UserTransaction

[DELTASPIKE-230] - Fallback stragtegy for resource bundles and locales

  [DELTASPIKE-223] - Add convention for @MessageResource annotated types.

resultClass=Employee.class

class Employee

createNamedQuery("findAllEmployeesInCity")

List<Employee>

@NamedNativeQuery

resultSetMapping="employee-address"

@SqlResultSetMapping(name="employee-address", entities={ @EntityResult(entityClass=Employee.class), @EntityResult(entityClass=Address.class)} )

are intuitive

High-Level Overview

essentially a security specific 'view' of the the currently executing user

instances are all bound to (and require) a

When you interact with a Subject, those interactions translate to subject-specific interactions with the SecurityManager

'umbrella’ object that coordinates its internal security components that together form an object graph

‘connector’ between Shiro and your

Shiro looks up many of these things from one or more Realms configured for an application

component responsible determining users' access control in the application

if a user is allowed to do something or not

knows how to create and manage user

lifecycles

Shiro has the ability to natively manage user Sessions in any environment, even if there is no Web/Servlet or EJB container available

Shiro will use

if available, (e.g. Servlet Container)

if there isn't one, such as in a standalone application or non-web environment, it will use its

exists to allow any datasource to be used to

performs Session persistence (CRUD) operations on behalf of the SessionManager

allows any data store to be plugged in to the Session Management infrastructure

creates and manages Cache instance lifecycles used by other Shiro components

improve performance while using these data source

‘connector’ between Shiro and your application’s security data

‘connector’ between Shiro and your application’s security data

‘connector’ between Shiro and your application’s security data

‘connector’ between Shiro and your application’s security data

elements of the user interface are displayed to the user based on the user's privilege level

assign permissions to individual objects within the application’s business domain

Permissions

Permissions assigned to user for a given resource in the tree are inherited by other resources

Permissions are inherited

persist user, group and role information in database. JPA implementation is his dream

Security Module Drafts

Identity

interface Identity

login()

logout()

getUser()

Events LoggedInEvent LoginFailedEvent AlreadyLoggedInEvent PreLoggedOutEvent PostLoggedOutEvent PreAuthenticateEvent PostAuthenticateEvent

Object level permission

Grant or revoke permissions

Group management

User/Identity management

identity.hasRole

identity.hasPermission

User, Group and Role

hooks for common IDM or Security operations

Audit and logging for permission and IDM related changes

Event API.

Impersonalization

Impersonalization

control which elements of the user interface are displayed to the user based on their assigned permissions

ask for permission

more advanced security resolution mechanisms

Rules based engine

external services - XACML

jboss.as.jpa.adapterModule

jboss.as.jpa.adapterClass

org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor

Working with other persistence providers

A project to build integration for persistence providers like EclipseLink, is here.

Troubleshooting

“org.jboss.as.jpa” logging can be enabled to get the following information: INFO - when persistence.xml has been parsed, starting of persistence unit service (per deployed persistence.xml), stopping of persistence unit service DEBUG - informs about entity managers being injected, creating/reusing transaction scoped entity manager for active transaction TRACE - shows how long each entity manager operation took in milliseconds, application searches for a persistence unit, parsing of persistence.xml

To enable TRACE, open the as/standalone/configuration/standalone.xml (or as/domain/configuration/domain.xml) file. Search for <subsystem xmlns="urn:jboss:domain:logging:1.0"> and add the org.jboss.as.jpa category

Packaging the Hibernate 3.5 or greater 3.x JPA persistence provider with your application

jboss.as.jpa.providerModule needs to be set to hibernate3-bundled.

<property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" />

Sharing the Hibernate 3.5 or greater JPA persistence provider between multiple applications

Applications can share the same Hibernate3 (for Hibernate 3.5 or greater) persistence provider by manually creating an org.hibernate:3 module (in the AS/modules folder). Steps to create the Hibernate3 module:

<property name="jboss.as.jpa.providerModule" value="org.hibernate:3" />

is security-specific view of the

and that Subject instances are always bound to a thread to ensure we know who is executing logic at any time during the thread's execution

Subject instance must be created

Subject instance must be bound to the currently executing thread

Subject must be unbound to ensure that the thread remains 'clean' in any thread-pooled environment

Shiro has architectural components that perform this bind/unbind logic automatically

root Shiro Filter performs this logic when filtering a request

after creating a Subject instance, it must be bound to thread

Test Setup

'setup' and 'teardown'

can be used in both unit testing and integration testing

AbstractShiroTest

abstract class AbstractShiroTest