IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-30 10:47:08 -06:00
Code Issues Packages Projects Releases Wiki Activity
8fcf6d6b34
freeipa/install/html/unauthorized.html

51 lines
1.4 KiB
HTML
Raw Normal View History

Main UI, migration, and html Style updates
2011-01-20 14:39:59 -06:00
<!DOCTYPE html>
Show (hopefully) useful information if the Kerberos connection fails.
2007-09-24 14:20:34 -05:00
<html>
Main UI, migration, and html Style updates
2011-01-20 14:39:59 -06:00
<head>
Fixed browser configuration pages The browser configuration pages have been modified to improve the content and appearance. Ticket #1624
2011-08-16 13:58:19 -05:00
<meta charset="utf-8">
Main UI, migration, and html Style updates
2011-01-20 14:39:59 -06:00
<title>IPA: Identity Policy Audit</title>
Load updated Web UI files after server upgrade 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
2013-08-29 08:19:02 -05:00
<script type="text/javascript" src="../ui/js/libs/loader.js"></script>
<script type="text/javascript">
(function() {
var styles = [
webui: apply PatternFly theme on config pages https://fedorahosted.org/freeipa/ticket/4278 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>
2014-03-31 07:03:28 -05:00
'../ui/css/patternfly.css',
'../ui/css/ipa.css'
Load updated Web UI files after server upgrade 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
2013-08-29 08:19:02 -05:00
];
ipa_loader.styles(styles);
})();
</script>
Main UI, migration, and html Style updates
2011-01-20 14:39:59 -06:00
</head>
Fixed: Duplicate CSS definitions https://fedorahosted.org/freeipa/ticket/1565 The ipa.css, ipa_error.css and ipa_migration.css contain some duplicate definitions which cause maintenance problems. Additional changes: * fixed whitespaces in ipa.css * unified headings in config pages
2011-10-11 02:42:35 -05:00
<body class="info-page">
error handling style modifying the directories so they find the assets in the right locations
2011-01-25 13:44:42 -06:00
webui: apply PatternFly theme on config pages https://fedorahosted.org/freeipa/ticket/4278 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>
2014-03-31 07:03:28 -05:00
<nav class="navbar navbar-default navbar-pf" role="navigation">
<div class="navbar-header">
<a class="brand" href="../ui/index.html"><img src="../ui/images/header-logo.png" alt="FreeIPA"></a>
</div>
</nav>
Fixed browser configuration pages The browser configuration pages have been modified to improve the content and appearance. Ticket #1624
2011-08-16 13:58:19 -05:00
webui: apply PatternFly theme on config pages https://fedorahosted.org/freeipa/ticket/4278 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>
2014-03-31 07:03:28 -05:00
<div class="container-fluid">
<div class="row">
<div class="col-sm-12">
Fixed browser configuration pages The browser configuration pages have been modified to improve the content and appearance. Ticket #1624
2011-08-16 13:58:19 -05:00
webui: apply PatternFly theme on config pages https://fedorahosted.org/freeipa/ticket/4278 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>
2014-03-31 07:03:28 -05:00
<h1>Unable to verify your Kerberos credentials</h1>
<p>
Please make sure that you have valid Kerberos tickets (obtainable via <strong>kinit</strong>), and that you have configured your browser correctly.
</p>
Fixed browser configuration pages The browser configuration pages have been modified to improve the content and appearance. Ticket #1624
2011-08-16 13:58:19 -05:00
webui: apply PatternFly theme on config pages https://fedorahosted.org/freeipa/ticket/4278 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>
2014-03-31 07:03:28 -05:00
<h2>Browser configuration</h2>
Fixed browser configuration pages The browser configuration pages have been modified to improve the content and appearance. Ticket #1624
2011-08-16 13:58:19 -05:00
webui: apply PatternFly theme on config pages https://fedorahosted.org/freeipa/ticket/4278 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>
2014-03-31 07:03:28 -05:00
<div id="first-time">
<p>
If this is your first time, please <strong>configure your browser</strong>.
Use <a href="browserconfig.html">Firefox configuration page</a> for Firefox
or <a href="ssbrowser.html">manual configuration page</a> for other browsers.
</p>
error handling style modifying the directories so they find the assets in the right locations
2011-01-25 13:44:42 -06:00
</div>
webui: apply PatternFly theme on config pages https://fedorahosted.org/freeipa/ticket/4278 Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>
2014-03-31 07:03:28 -05:00
</div>
</div>
Fixed browser configuration pages The browser configuration pages have been modified to improve the content and appearance. Ticket #1624
2011-08-16 13:58:19 -05:00
</div>
Main UI, migration, and html Style updates
2011-01-20 14:39:59 -06:00
Show (hopefully) useful information if the Kerberos connection fails.
2007-09-24 14:20:34 -05:00
</body>
Main UI, migration, and html Style updates
2011-01-20 14:39:59 -06:00
Show (hopefully) useful information if the Kerberos connection fails.
2007-09-24 14:20:34 -05:00
</html>
Reference in New Issue Copy Permalink