freeipa/install/ffextension/install.rdf

<?xml version="1.0"?>
<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:em="http://www.mozilla.org/2004/em-rdf#">

    <Description about="urn:mozilla:install-manifest">

        <em:id>kerberosauth@redhat.com</em:id>
        <em:name>Kerberos Configuration</em:name>
        <em:version>0.1</em:version>
        <em:description>Configures browser to use negotiate authentication</em:description>
        <em:type>2</em:type>
        <em:creator>Red Hat, Inc.</em:creator>
        <em:developer>Petr Vobornik</em:developer>
        <em:homepageURL>http://www.redhat.com/</em:homepageURL>
        <em:bootstrap>true</em:bootstrap>

         <!-- Firefox -->
        <em:targetApplication>
            <Description>
                <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
                <em:minVersion>10.0</em:minVersion>
                <em:maxVersion>15.0.*</em:maxVersion>
            </Description>
        </em:targetApplication>
    </Description>
</RDF>
Kerberos authentication extension The extension should replace signed code (configure.jar) used for Firefox configuration. Using privileged code is not possible since Firefox 15 [1] [2]. Extension is bootstrapped which means it can be used without browser restart on Firefox 4 and later. How it works: Extension listens on each page's document element for event 'kerberos-auth-config' which should be raised on custom data element. Communication data is transferred through data element's attributes [3]. The only required attribute is 'method'. Currently there are two possible values: 'configure' and 'can_configure'. 'can_configure' method serves for detecting if the extension is installed. 'configure' method does the actual configuration. Possible optional options for 'configure' can be found in kerberosauth.js:kerberosauth.config_options. Currently they are: 'referer', 'native_gss_lib', 'trusted_uris', 'allow_proxies'. Result of a method is stored in data element's 'answer' attribute. When 'configure' method is used, the extension asks the user if he wants to configure the browser, it should prevent silent configuration by malicious pages. Possible enhancement: * add UI for manual edit * more configurations ie. for gss_lib, sspi (good with UI or with enhanced config page) * introspection of client (read ipa client install config and such) Ticket: https://fedorahosted.org/freeipa/ticket/3094 [1] https://bugzilla.mozilla.org/show_bug.cgi?id=546848 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=757046 [3] https://developer.mozilla.org/en-US/docs/Code_snippets/Interaction_between_privileged_and_non-privileged_pages 2012-10-01 10:25:08 -05:00			`<?xml version="1.0"?>`
			`<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"`
			`xmlns:em="http://www.mozilla.org/2004/em-rdf#">`

			`<Description about="urn:mozilla:install-manifest">`

			`<em:id>kerberosauth@redhat.com</em:id>`
			`<em:name>Kerberos Configuration</em:name>`
			`<em:version>0.1</em:version>`
			`<em:description>Configures browser to use negotiate authentication</em:description>`
			`<em:type>2</em:type>`
			`<em:creator>Red Hat, Inc.</em:creator>`
			`<em:developer>Petr Vobornik</em:developer>`
			`<em:homepageURL>http://www.redhat.com/</em:homepageURL>`
			`<em:bootstrap>true</em:bootstrap>`

			`<!-- Firefox -->`
			`<em:targetApplication>`
			`<Description>`
			`<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>`
			`<em:minVersion>10.0</em:minVersion>`
			`<em:maxVersion>15.0.*</em:maxVersion>`
			`</Description>`
			`</em:targetApplication>`
			`</Description>`
			`</RDF>`