|
|
| (7 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | == Configuration ==
| + | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} |
| − | NOTE: The XML File Context Provider configuration XML file format was designed to be used to configure any number and type of Context Provider. Other Higgins Context Providers contributed by Novell currently use this same format. Work is currently underway which may change or eliminate this method of CP configuration.
| + | The XML File Context Provider is an implementation of the Higgins IdAS API that retrieves and stores data in an XML file. |
| | | | |
| − | The XML File Context Provider is configured through an XML file whose format is specified by the following XML schema:
| + | ==Details== |
| | + | * ''Status'': Available from M0.9 |
| | + | * ''Language'': Java |
| | + | * ''Bindings'': Current: Java; |
| | + | * ''Packaging'': JAR |
| | | | |
| − | [https://forgesvn1.novell.com/viewsvn/bandit/trunk/IdentityAbstraction/conf/realms.xsd?content-type=text%2Fplain Configuration XML Schema]
| + | ==Plan== |
| | + | * [[XMLFILE_CP_ToDo | XML File CP Roadmap]] |
| | | | |
| − | Two example configuration files ([http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/plugins/org.eclipse.higgins.idas.cp.xmlfile.test/testReaml.xml?root=Technology_Project&view=markup testRealm.xml]) and ([http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/plugins/org.eclipse.higgins.idas.cp.xmlfile.test/testReaml2.xml?root=Technology_Project&view=markup testRealm2.xml]) are available in the org.eclipse.higgins.idas.cp.xmlfile.test project. Instructions on how to access this project is available here: [[XML_File_CP_CVS | XML File CP Projects]].
| + | ==Service== |
| − | | + | * [[XML File CP Configuration]] |
| − | Each Context configuration section is described by a "Realm" definition within the XML file. For purposes of this documentation, the terms "Realm" and "Context" are synonymous.
| + | |
| − | | + | |
| − | ===Realm Configuration Elements===
| + | |
| − | ====realms====
| + | |
| − | This element should encapsulate all realm definitions and other global configuration. This element should also define the namespaces to be used globally throughout the configuration document.
| + | |
| − | | + | |
| − | <pre>
| + | |
| − | <bci:realms
| + | |
| − | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| + | |
| − | xmlns:bci="http://www.bandit-project.org/commonidentity"
| + | |
| − | xmlns:xacml="urn:oasis:names:tc:xacml:2.0:policy:schema:os"
| + | |
| − | xsi:schemaLocation="urn:oasis:names:tc:xacml:2.0:policy:schema:os:access_control-xacml-2.0-policy-schema-os.xsd">
| + | |
| − | ...
| + | |
| − | </bci:realms>
| + | |
| − | </pre>
| + | |
| − | | + | |
| − | ==XML File CP TODO==
| + | |
| − | | + | |
| − | # The getSchema() needs to be updated to follow the latest ontology.
| + | |
| − | # The format of the identity data should more closely follow the Higgins data model and, since we control it, we can structure the XML however we want. Besides, I don't like the file format as it stands anyway. In addition, if we structure it right, we won't have to do any mapping of types from the XML to Higgins, it can just BE what we expect in Higgins or even the consuming application (ie. CardSpace claims). At any rate, currently, that's not the case.
| + | |
| − | # Respond to registry and configuration model changes when they are completed. #2 should be done in conjunction w/ this.
| + | |
| − | # Allow updates through IdAS APIs.
| + | |
| | | | |
| | == See Also == | | == See Also == |
| | * [http://www.eclipse.org/higgins Higgins Home] | | * [http://www.eclipse.org/higgins Higgins Home] |
| | * [[Components]] | | * [[Components]] |
| | + | [[Category:Higgins Components]] |
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
The XML File Context Provider is an implementation of the Higgins IdAS API that retrieves and stores data in an XML file.
