![]() ![]() In the Identity Administration portal, add the application and configure application settings.įor details, see Configure Hightail in the Identity Administration portal. For this reason, there are two parts to configuring the Hightail website one before configuration in the Identity Administration portal and one after. ![]() You will need to copy some settings from the Identity Administration portal into the Hightail website, and you will need to copy some settings from the Hightail website into the Identity Administration portal. ![]() You will need to copy some settings from the Hightail website into the Identity Administration portal. This function is called automatically once the DOM content is done loading, and is passed a single parameter - the provider instance whose data is being displayed.The following is an overview of the steps required to configure the Hightail Web application for single sign-on (SSO) via SAML.Ĭreate Hightail user accounts and make sure you have a Hightail account with administrator rights to configure SSO.Ĭonfigure the Hightail application for single sign-on (part 1).įor details, see Configure Hightail on its web site (part 1). The XHTML page should have a function in the global scope called onLoadProvider. The content to the right of the menulist is an IFrame, pointed at a URL read from the providers managementURL attribute, which should point to an XHTML page. Once an account has been created, it is manageable from within the Preferences dialog, in the Attachment pane, in the Outgoing tab. The Hightail settings.xhtml and settings.js file have examples of this. Once this is done, the field is accessible from within the implementation via the Preferences API using the key mail.cloud_KEY.username where ACCOUNT_KEY is the value passed into the implementations init function. In this example, the username value is read from the input, and then the specially-crafted object is returned. Providers need only provide an extraArgs function in the IFrame content which returns an object specifying the name, type, and value to save.įIELD_NAME: , Saving the preferences is handled automatically by the dialog code. Saving custom settings in preferencesĬustom settings for a provider are saved using the Preferences API. The button to set up the account will only become enabled once the checkValidity method for the form returns true. For each input event, the checkValidity method of the form is automatically called. The form is expected to use HTML5 form validation. To handle custom settings, the settings XHTML page should contain a form with the id " provider-form", with its onsubmit attribute set to "return false ". Note: The setup dialog window should resize itself automatically in order to fit the content of the IFRAME without scrollbars. That URL is then loaded into an IFrame directly beneath the provider menulist. Other services may require the user to fill in a server string or port number.Ī provider implementation can choose what information it gets from the user from the setup dialog by pointing the settingsURL attribute of their nsIMsgCloudFileProvider implementation to a chrome URL for an XHTML page that contains a form with the extra information. Hightail, for example, requires a username and password. Other providers however may require the user to fill in additional details in order to connect to the service. Some providers require Thunderbird to do very little in order to connect a user to their account. The account setup dialog allows the user to select what account type they would like to create from a menulist. See cloudfile/cloudFileComponents.manifest for an example, as well as this document on chrome.manifest files. Also, you must add the component's contract ID to the "cloud-file" category. If the nsIMsgCloudFileProvider is being created as part of an add-on, the add-on must register the component in chrome.manifest. If the provider is being merged into the comm-central code repository (and thus added to the official Thunderbird build), you must also add the components to the cloudfile/cloudFileComponents.manifest, cloudfile/jar.mn, and installer/package-manifest.in. The nsIMsgCloudFileProvider implementation must be registered as a component. The Hightail implementation is a great place to look for examples and inspiration. Both refer to the Filelink feature.įilelink storage providers must implement the nsIMsgCloudFileProvider interface. Note: Cloudfiles and BigFiles were the two temporary feature names that were used while Filelink was under construction. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |