Technology

When a user account becomes locked out, the cause is often attributed to a user who has simply entered an old or incorrect password too many times. However, this is far from being the only thing that can cause an account to become locked. Another common cause, for example, is an application or script that is configured to log into the system using an old password. Perhaps the most easily overlooked cause of account lockouts, however, is the use of cached credentials. Before I explain why cached credentials can be problematic, let’s first consider what the Windows cached credentials do and why they are necessary. Cached and stored credentials Cached credentials are a mechanism that is used to ensure that users have a way of logging into their device in the event that the device is unable to access the Active Directory. Suppose for a moment that a user is working from a domain-joined laptop and is connected to the corporate network. In that type of situation, the Active Directory would authenticate the user’s credentials when the user logs on. If, on the other hand, the user is working from home using the same laptop but has no connection to the corporate network, then the Active Directory cannot process the user’s logon request. This is where cached credentials come into play. If it were not for cached credentials, then the user would be unable to log on to their device because there is no domain controller available to process the logon request. Because Windows supports the use of cached credentials, however, the cached credentials residing within the user’s device can process the authentication request. The user will not be able to access any of the resources on the corporate network because no connection to the network exists and the user’s authentication was not processed by a domain controller. Even so, the user will at least have the ability to log into their laptop and use any applications that are installed locally on the device. Even though cached credentials are primarily used as a mechanism for allowing users to login locally when they are working from outside of the office, cached credentials have another important use. If an organization were to suffer a catastrophic failure that resulted in an Active Directory outage, then the IT staff could use cached credentials as a means of logging into their devices so that they can begin diagnosing and repairing the Active Directory problems. All of this is to say that Windows cached credentials do have a valid use case. As such, they are not the sort of thing that you would want to disable. As previously noted however, the use of cached credentials can cause confusion and even cause accounts to become locked out under certain circumstances. Cached credentials causing account lockouts Imagine for a moment that a user works from two domain joined devices: a corporate desktop, and a laptop. Now suppose that the user is working from their desktop and changes their Windows password. Assuming that the laptop is powered off at that point, the laptop is unaware of the password change. It still has the user’s old credentials stored in the password cache. With that in mind, consider what would happen the next time that the user attempts to logon from their laptop. If the user is not connected to the corporate network, then their new password will not work because the old password is still stored in the cache. However, the user can still log into the device using their old password. Once the user connects to the corporate network, however, the password will be updated. This means that if the user repeatedly attempts to log on to their laptop using their old password, then the authentication process will fail, and the user will eventually be locked out of their account. Updating user cached credentials Specops uReset can help with this problem. Users are able to reset their Windows passwords directly from the Windows logon screen. More importantly, when a user changes or resets their password, the Specops uReset software automatically synchronizes the new password across the user’s devices, updating the local cache in the process. This means that a user should never run into a situation in which some devices have been updated with their new password while other devices continue to use the old password. From an IT standpoint, this means fewer password-related service calls to your helpdesk. NOTE:: This article is copyright bythehackernews.com and we are using it for educational or Information purpose only

There are essentially two types of websites: static and dynamic. However this can be confusing because there can be static elements of a dynamic site, dynamic elements of a static site… as we continue into the age of Progressive Web Apps and website personalization, the lines become blurred between what’s static and dynamic. What can be Static or Dynamic? When discussing whether a site is static or dynamic, half of the battle is determining what aspect of the site you’re discussing. The code of the page, delivery of the page, and the client browser can all be considered either static or dynamic. Code The code of a webpage can be either static or dynamic. This is fairly straightforward: static content is content that is hard-coded on a page. Dynamic pages are structured by referencing a CMS or some external database. Delivery The delivery of a webpage can also be either static or dynamic. Static delivery is pre-rendered pages that are typically cached and delivered via a content delivery network, or CDN. Dynamic pages are generated in real time at the time of the request by the server. Client Browser The browser can also affect whether a site is static or dynamic. Static sites remain the same for all who access it, regardless of browser. Dynamic pages can use client side Javascript to make pages dynamic in real time. Main Differences Between Dynamic (Server Rendered) and Static (Pre-Rendered) Sites As a rule of thumb, dynamic sites use server side languages to process requests at the time it’s made and generate a page and its contents in real-time. Static pages are pre-rendered, cached, and delivered to the user. When we think back to the beginnings of the internet, all web pages displayed the same content to every user. Over time, websites integrated with databases powered by languages like Python, PHP, ASP, Ruby, Java, and more. This enabled sites to be dynamic, and display relevant content to the user based on a setting or input. Before proceeding, it’s important to understand that for our purposes in this article, dynamic and static refer to how a page is being delivered to the user. Sites can be dynamically generated, cached, and served statically. Static sites can have dynamic components. What we’re referring to throughout this article is generally how a site is rendered, either by the server at the time of the request (dynamic) or pre-rendered and delivered via CDN (static). What’s a Dynamic Website? Dynamic sites use server side languages to process requests at the time it’s made and generate a page and its contents in real-time. This means that dynamic websites interact with the user accessing the site and render content depending on the user’s actions or settings. One example of a dynamic website is web apps. Take Twitter as an example: when you log in, it displays content just for you. While dynamic sites are extremely powerful they are also more complex. Along with this complexity are many advantages and disadvantages inherent to a dynamic site build. Dynamic Site Advantages Powered by Databases By connecting a dynamic site to a database, you’re able to easily request information in an organized and structured way to create and display content depending on how the user wants to view it. Connect to a CMS This ability to connect to a database means that you can also connect to a CMS. Content stored in the CMS can be a variety of things, from the text to the images that are displayed, page layouts, site settings, and more. This allows for extreme flexibility when building sites, and also allows for multiple users to be able to manipulate content as needed. Low Ongoing Maintenance Cost Since you can connect a dynamic site to a CMS there are little or no ongoing costs unless there is a change in the basic design or an extra capability is added to the site. Dynamic Site Disadvantages Design Limitations When generating content on a page from a database, you’re typically pulling in content and telling it to display a certain way, no matter what the content is. This can make design tricky, as you’ll likely opt for a one-size-fits-all approach. Depending on the CMS, it can be difficult to build multiple designs to display different types of content in different types of ways. With dynamic sites, you are forced into using templates for your page, or you are committing to building custom templates for every page. This is easier in some CMSes but harder to do in others such as WordPress or Drupal. Can Incur Upfront Build Costs When building a dynamic site, it can incur much more work upfront as you’re connecting the site to a database, building the foundation for the site to generate content, etc. Additional functionality may also cost more as you add features to your dynamic site throughout its life. While maintenance costs are low for a dynamic site, they can incur much higher initial build costs than a static site. What’s a Static Website? Static websites are pre-rendered, typically cached, and served by a CDN. The site is pre-generated by individual files that are delivered to all users in the same manner. There are advantages and disadvantages to choosing to build a static site. Static Site Advantages Flexibility The main advantage of a static site is the flexibility it offers. Every page can be different; designs can change, layouts can differ, and the designer doesn’t have to make one design fit the mold for multiple types of content to display on a page. Cost Cost can be lower upfront to build a static site than to build a dynamic site. Since pages don’t have to be connected to a database to generate content and render the view, they can be less expensive than a dynamic site to build. However, hooking up a headless CMS to a static site generator and then a delivery network can make a static site expensive to build. Load Times Since static sites

One of the most important decisions to make before having a website built for you is whether to choose a static website or a content management system, known as a CMS. There are advantages to both but choosing one over the other is a matter of determining what your needs are. What is a Static Website? Static or fixed websites are usually brochure type sites where the content does not need to change often or at all and where the number of pages is typically low. Updates can be made but will usually have to be done by a web developer or by someone with a rudimentary knowledge of how to use html and ftp. Disadvantages of having a static site potential difficulty in updating. Even a slight mistype within the code could disrupt the layout or operation of the web page increased cost paid to a web developer for changes. search engine optimization – or SEO – will not favor websites with static content over a similar site that has its content regularly updated. Advantages of having a static site Lower development cost. Static sites are usually built in a fraction of the time that a CMS will take. Simple web hosting needs. Static sites do not generally need a database to store their contents in and can be hosted with your local cable company which often gives around 5MB of space to users. Possible to build your own with WYSIWYG tools. There are many low-cost software packages designed to allow you to make your own website visually, without much knowledge of HTML. However, if your website is for your business, it would be in your best interest to have it look as professional as possible. What is a Content Management System? A CMS is a dynamic website which is designed to be scalable in at least its content, and most often its features. The user is empowered to update content at their leisure and usually without any concern for breaking the website layout as this is usually under tight control of the CMS itself. Frequent updates can be made to web pages, blogs, photo galleries and more. Google’s Blogger is a basic content management system which has no cost to setup and while it is useful for a personal site, it has limited value as a business site. A more advanced system is WordPress which is maturing quickly from initially being a blogging tool to a more fully featured CMS. Drupal is an example of a complete CMS, designed to be fully scalable, adaptive and feature rich. Disadvantages of a CMS: Greater cost of development. As it takes much more time to develop a database-driven CMS and as it usually requires specific knowledge of a particular CMS, it will require a greater investment. However, like is also likely to result in a greater return on investment (ROI). Learning Curve. To understand how to work with a CMS, you will need to learn how it is structured so you can control menus, naming, categories, etc. Slower bandwidth customers may have a slightly longer wait. Content Management Systems often include more media such as images and dynamic content. This is typically not a concern for most modern countries with high speed access but it should be stated nonetheless. Advantages of a CMS extensive or full control over the content of your site without the need for knowledge of HTML, CSS or other web languages. Changes can be made at your leisure. Depending on what type of CMS you choose, there can be a wide array of content types to work with beyond just text, such as photos, audio, video. SEO Friendly. Websites which update content on a regular basis gain more of a spotlight from search engines and will often rank higher in search engine results (SER) pages which is an important competitive factor for business websites.