| RE: [higgins-dev] Another Topic for F2F |
|
There are two
possible deployment architectures for an Identity Agent: one where HBX includes
the card selector UI and relies on the rest of the agent being hosted. The
other (the one that I bet Pat is talking about), is where HBX merely invokes a
local rich client app that provides the card selector UI (and the I-Card
Registry an embedded (or separate?) Token Service), etc. This second one
is most like the MSFT CardSpace deployment architecture. For the first
architecture we are well on our way with Jan, Abhi & co developing the “in-HBX”
card selector UI for use with a remote service. But for the second architecture
that uses/includes the “ISS Client UI” component shown at the top
of this diagram we
have barely started. The original idea was that ISS Client UI (which, as I’ve
said when bundled with all the other require components is roughly like MSFT
CardSpace app/sub-system) would be an Eclipse RCP app that would use SWT, and
thus be fully natively compile-able to binary (as has been proven with the rest
of the Eclipse IDE). In any event
this is a wonderful topic. If folks would
like to talk sooner than the F2F, please suggest some times. Friday afternoon
PT is best for me this week. Wed (tomorrow) is terrible. Thursday after the
Higgins call is a possibility though not great. -Paul From:
higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Anthony Nadalin I'm not sure what you are proposing, is there
something specific you want the Higgins selector service to support ?
|
"Pat
Felsted" <PFELSTED@xxxxxxxxxx>
