Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [higgins-dev] Notes from a teleconf meeting wrt IGF
Note that there are also methods for programmatically registering context factories at runtime: IdASRegistry.registerContextFactory()
They take one or more context types, and the class name or instance of a context factory.

It's not currently possible to register context IDs programmatically, but if this is needed it should be very easy to implement.

Markus

On Nov 29, 2007 6:02 AM, Jim Sermersheim < jimse@xxxxxxxxxx> wrote:

Phil, there's some text at http://wiki.eclipse.org/IdAS_Basic_Deployment#Edit_the_configuration_file which describes two different methods for doing IdAS context registration/configuration.


While the first way uses a configuration file on disk, that's only one way of creating and configuring the IdASRegistry.  In theory, we should be able to create the entire configuration at runtime as a Map object, and pass that to IdASRegistry.configure.  That assumes there's some way (at runtime) to know how to build that Map object.


A middle-ground alternate would place static configuration data in the config file, then at runtime, after populating the ConfigurationHandler, get the Map (ConfigurationHandler.getSettings ), inject the remaining (dynamic) config settings into the Map, pass that updated Map back into ConfigurationHandler.config, and continue as normal.


At least I think that should work -- it might be a good exercise to test it with the BasicIdAS deployment.


Jim

>>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 11/28/07 3:14 PM >>>

So, we may need to flesh out our capabilities in these areas.  We can access attributes in IdAS, and we can get/set policy on a context factory (though we've yet to demonstrate what that looks like), but we don't yet have the ability to express policy at the Context or DigitalSubject level.  This is stuff that has sort of been on the back burner.

>>> Anthony Nadalin <drsecure@xxxxxxxxxx> 11/28/07 2:00 PM >>>

Not seeing any value with IGF, we already have claims and policy that can express what IGF is supposed to be able to express, so maybe the IGF folks can just pickup what has been done with defining the claims.

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122

Inactive hide details for


From:


"Jim Sermersheim" <jimse@xxxxxxxxxx>


To:


<higgins-dev@xxxxxxxxxxx>


Date:


11/28/2007 02:45 PM


Subject:


[higgins-dev] Notes from a teleconf meeting wrt IGF





To try and push ahead on fleshing out what it would take to consume Higgins by the IGF, or implement parts of it in Higgins, we had a chat on the phone with Phil Hunt. Primarily, the call was geared toward sharing descriptions of architecture (understanding how IdAS works and understanding the IGF architecture).  

I put notes here http://wiki.eclipse.org/20071128_IGF_teleconf_notes  
which are pointed at from here http://wiki.eclipse.org/IGF_Integration  
which is pointed at from here http://wiki.eclipse.org/Identity_Attribute_Service  


I'll start a new thread (continuing an old one) on Idas API extensibility which was one of the work items that came from the call. 


Jim _______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev


_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev


Back to the top