Comments for Analyzing Identity

Comment on Part One: Software Development Lifecycle (Architecture and Design) by Gerry Gebel – Axiomatics: Part One: Software Development Lifecycle (Architecture and Design) http… « oracle fusion identity

Thu, 05 Apr 2012 21:52:19 +0000

[...] Gebel – Axiomatics: Part One: Software Development Lifecycle (Architecture and Design) http://analyzingidentity.com/2012/04/05/part-one-software-development-lifecycle-architecture-and-des… https://plus.google.com/113340044616880088383/posts/cg5M4f1Ccnv http://bit.ly/OracleIdM Share [...]

Comment on Part Three: Enterprise Authorization Scenarios with James McGovern by Gerry Gebel – Axiomatics: Part One: Software Development Lifecycle (Architecture and Design) « oracle fusion identity

Thu, 05 Apr 2012 21:41:25 +0000

[...] Enterprise Architect for HP focused on insurance and I held several discussions (Part 1, Part 2, Part 3) on using entitlements management within the insurance vertical. Now that we are in a new year, we [...]

Comment on Part Two: Insurance Authorization Scenarios with James McGovern by Gerry Gebel – Axiomatics: Part One: Software Development Lifecycle (Architecture and Design) « oracle fusion identity

Thu, 05 Apr 2012 21:41:21 +0000

[...] the lead Enterprise Architect for HP focused on insurance and I held several discussions (Part 1, Part 2, Part 3) on using entitlements management within the insurance vertical. Now that we are in a new [...]

Comment on Part One: Insurance Authorization Scenarios with James McGovern by Gerry Gebel – Axiomatics: Part One: Software Development Lifecycle (Architecture and Design) « oracle fusion identity

Thu, 05 Apr 2012 21:41:18 +0000

[...] now is the lead Enterprise Architect for HP focused on insurance and I held several discussions (Part 1, Part 2, Part 3) on using entitlements management within the insurance vertical. Now that we are in [...]

Comment on Part Three: Enterprise Authorization Scenarios with James McGovern by Part One: Software Development Lifecycle (Architecture and Design) « Analyzing Identity

Thu, 05 Apr 2012 21:27:48 +0000

Comment on Part Two: Insurance Authorization Scenarios with James McGovern by Part One: Software Development Lifecycle (Architecture and Design) « Analyzing Identity

Thu, 05 Apr 2012 21:27:44 +0000

Comment on Part One: Insurance Authorization Scenarios with James McGovern by Part One: Software Development Lifecycle (Architecture and Design) « Analyzing Identity

Thu, 05 Apr 2012 21:27:42 +0000

Comment on Take 2, talking authZ with Gunnar by Take 3, talking authZ and TOCTOU with Gunnar « Analyzing Identity

Take 3, talking authZ and TOCTOU with Gunnar « Analyzing Identity — Fri, 18 Mar 2011 15:28:58 +0000

[...] to my colleagues, David Brossard and Pablo Giambiagi, for their input. You can also find part 1 and part 2 of the conversation on this [...]

Comment on The Anywhere Application Architecture by Take 3, talking authZ and TOCTOU with Gunnar « Analyzing Identity

Take 3, talking authZ and TOCTOU with Gunnar « Analyzing Identity — Fri, 18 Mar 2011 15:28:46 +0000

[...] talked previously about the XACML Anywhere Architecture where a callback from a Cloud Provider queries PDP; this would enable the Cloud Provider to get the [...]

Comment on Talking authorization with Gunnar Peterson by Take 3, talking authZ and TOCTOU with Gunnar « Analyzing Identity

Take 3, talking authZ and TOCTOU with Gunnar « Analyzing Identity — Fri, 18 Mar 2011 15:28:40 +0000

[...] also to my colleagues, David Brossard and Pablo Giambiagi, for their input. You can also find part 1 and part 2 of the conversation on this [...]