Recorded at SpringOne2GX 2013 in Santa Clara, CA. Speaker: Dr. David Syer The OAuth2 specification (wisely) leaves a lot of areas open to interpretation and implementation details, so there are a lot of opportunities to impose interpretations on the flows and the underlying data. This presentation starts with a basic guide to the main features of OAuth2 and then goes on to show, with examples, how they can be exploited to support business and application use cases. For instance, should you encode access decision data directly in the access token, or make the token completely opaque? Should you be signing requests? What naming convention should you use for OAuth2 scopes? How do you go about registering users and clients? There are some obvious patterns in existing OAuth2 implementations, and Spring Security OAuth provides plenty of hooks and extension points should you wish to copy one of those, or make your own rules. Examples will use Spring and Spring Security to show how to take advantage of the inherent flexibility, both in the spec and in the libraries. Learn more about Spring Security OAuth: http://projects.spring.io/spring-security-oauth and Spring Security: http://projects.spring.io/spring-security
workflows, innovative multi-channel support and a damn fine user experience that includes touch devices), and brief tutorials on solving some key content management challenges faced by Spring developers. There will also be a quick detour into Magnolia's Groovy shell and MagLev, a Grails plugin for Magnolia.
detailed guide to Identity Management with Spring Security. Spring developer and also Cloud Foundry engineer, Dave Syer, covers Single Sign On, security standards (including SAML, OpenID, OAuth, SCIM, JWT), how Spring Security can fit in, as well as demoing identity management as a service. Dave has tackled
Colocated transactions: If each logical partition were to own the entire transactional working set then highly applications can scale linearly if the concurrent transaction load is uniformly spread across the data set and hence across all the partitions. Each partition can coordinate its transaction without
Validates correct configuration of Neo4j and Spring, especially transaction-managers
enable Spring's Transaction Management infrastructure along with SDG's GemfireTransactionManagerto manage local, cache transactions for either Pivotal GemFire or Apache Geode. Declares and registers SDG's GemfireTransactionManager as the transactionManagerin Spring's Transaction Management infrastructure
advice provided through configuration. To enable batching of messages in a single transaction, use theTransactionInterceptor and the RepeatOperationsInterceptor inthe advice chain (with or without a transaction manager set in the baseclass). Instead of receiving a single message and processing it, thecontainer
Build a step that executes the flow provided, normally composed of other steps. The flow is not executed in atransaction because the individual steps are supposed to manage their own transaction state.
Exception class that indicates a rejected message on shutdown. Used to trigger a rollback for anexternal transaction manager in that case.
The EnableGemfireCacheTransactions annotation enables Pivotal GemFire or Apache Geode Cache Transactionsin Spring's Transaction Management infrastructure.