mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-28 01:41:14 -06:00
b4fc6f4ba8
Issue: * There was no caching policy specified. * -> Browsers use their own default policy. * -> After upgrade, some Web UI files might have been actualized some not. * -> With schema change may result into weird bugs in Web UI Solution considerations: 1. Detect server version change and hard-reload at runtime Detection is easy. Problem is the reload. Obvious candidate 'window.location.reload(true)' works in Firefox but not in Chrome because expected behavior when parameter is used is not in standard and therefore Chromium/WebKit authors did not implement it. 2. Application Cache HTML 5 technology which lets web apps to run offline. Besides weird issues with event handlers which I encountered, this would be an ideal candidate. Simple change of manifest file would lead to reload of all files (requires reload of page to used the new files). Showstopper was usage with untrusted certificate. If user did not add exception for the cert or its CA and would visit the page for a second time, all AJAX calls would fail. 3. Set Expires to now() for everything Web UI rarely changes so this is an overkill. Setting it to different value is not a solution either. We can't predict when the upgrade will happen and when new Web UI will be needed. Solution: * Implemented a mini loader which loads basic resources. Dojo loader takes action after Dojo is loaded. * The loader adds a version parameter (?v=__NUM_VERSION__) to all requests. * Version is defined in the loader. It's set to current in `make version-update`. * All static pages use this loader to fetch their resources. * Version is also passed to dojo loader as cache-bust for the same effect. * Expire header was set to 'access time plus 1 year' for /ui folder. Exceptions are HTML files and loader (set to immediate expiration). Possible issues: * Images are cached but not requested with version param. * Images with version and without are considered different * -> We would have to attach version to all URIs - in CSS and in JS. But we should avoid changing jQuery UI CSS. * Proposed solution is to change image name when changing image. Image change is done rarely. * Version is set by build and therefore updated just on server update. It might cause trouble with different update schedule of plugins. * No action taken to address this issue yet. * We might leave it on plugin devs (own .conf in /etc/httpd/conf.d/) * or set expires to now for all plugins * running `make version-update` is required in order to use static version of UI for testing https://fedorahosted.org/freeipa/ticket/3798
107 lines
3.9 KiB
HTML
107 lines
3.9 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<title>IPA: Identity Policy Audit</title>
|
|
<script type="text/javascript" src="../ui/js/libs/loader.js"></script>
|
|
<script type="text/javascript">
|
|
(function() {
|
|
var styles = [
|
|
'../ui/jquery-ui.css',
|
|
'../ui/ipa.css',
|
|
'ipa_error.css'
|
|
];
|
|
var scripts = [
|
|
'../ui/js/libs/jquery.js',
|
|
'../ui/js/libs/jquery-ui.js',
|
|
'krb.js',
|
|
'ffconfig.js',
|
|
'ffconfig_page.js'
|
|
];
|
|
ipa_loader.scripts(scripts);
|
|
ipa_loader.styles(styles);
|
|
})();
|
|
</script>
|
|
</head>
|
|
|
|
<body class="info-page">
|
|
|
|
<div class="container_1">
|
|
|
|
<div class="header-logo">
|
|
<img src="../ui/images/ipa-logo.png" /><img src="../ui/images/ipa-banner.png" />
|
|
</div>
|
|
|
|
<div class="textblockkrb browser-config">
|
|
<h1>Firefox configuration</h1>
|
|
|
|
<div id="wrongbrowser" style="display:none">
|
|
<h2>Wrong Browser!</h2>
|
|
<p>
|
|
<a href="ssbrowser.html" id="notfirefox-link">Proceed to configuration for other browsers</a>
|
|
</p>
|
|
<p>
|
|
You are not using Firefox. Please use configuration page for other browsers.
|
|
</p>
|
|
</div>
|
|
|
|
<div id="step1">
|
|
<h2>Step 1</h2>
|
|
<p>
|
|
<a href="ca.crt" id="ca-link">Import Certificate Authority certificate</a>
|
|
</p>
|
|
<p>
|
|
Make sure you select <b>all three</b> checkboxes.
|
|
</p>
|
|
</div>
|
|
|
|
<div id="step2a" style="display:none">
|
|
<h2>Step 2a</h2>
|
|
<p>
|
|
<a href="ssbrowser.html#oldfirefox" id="oldfirefox-link">Proceed to configuration page for older versions of Firefox</a>
|
|
</p>
|
|
<!--<p id="older-compatible">
|
|
Your version of Firefox can be configured by an older method. You don't have to use the Kerberos Configuration extension.
|
|
</p>-->
|
|
<p id="older-required">
|
|
Your version of Firefox is not compatible with configuration method on this page. Please use configuration page for older versions of Firefox.
|
|
<p>
|
|
</div>
|
|
|
|
<div id="step2">
|
|
<h2>Step 2</h2>
|
|
<div id="ext-installed">
|
|
<p>
|
|
<a href="kerberosauth.xpi" id="reinstall-link">Re-install extension</a>
|
|
</p>
|
|
<p>
|
|
Extension installed. You can proceed to Step 3.
|
|
</p>
|
|
</div>
|
|
<div id="ext-missing">
|
|
<p><a href="kerberosauth.xpi" id="install-link">Install Kerberos Configuration Firefox extension</a></p>
|
|
<p>Kerberos Configuration extension is required for Step 3</p>
|
|
</div>
|
|
</div>
|
|
|
|
<div id="step3">
|
|
<h2>Step 3</h2>
|
|
<p><a href="#configure-browser" id="configure-link">Configure browser</a></p>
|
|
<p id="config-success" style="display:none">Browser successfully configured</p>
|
|
<p id="config-aborted" style="display:none">Configuration aborted</p>
|
|
<p id="config-noext" style="display:none">Configuration was not successful, extension isn't installed or is disabled. Please proceed to step 2.</p>
|
|
<p id="config-error" style="display:none">Configuration was not successful, unknown error uccured.</p>
|
|
</div>
|
|
|
|
<div id="step4">
|
|
<h2>Step 4</h2>
|
|
<p><a href="../ui/index.html" id="return-link">Return to Web UI</a></p>
|
|
</div>
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</body>
|
|
|
|
</html>
|