Home » Users
Category Archives: Users
Periodically Unlock Items of Idle Users in Sitecore
In my last post I showed a way to unlock locked items of a user when he/she logs out of Sitecore.
I wrote that article to help out the poster of this thread in one of the forums on SDN.
In response to my reply in that thread — I had linked to my previous post in that reply — John West, Chief Technology Officer of Sitecore, had asked whether we would also want to unlock items of users whose sessions had expired, and another SDN user had alluded to the fact that my solution would not unlock items for users who had closed their browser sessions instead of explicitly logging out of Sitecore.
Immediate after reading these responses, I began thinking about a supplemental solution to unlock items for “idle” users — users who have not triggered any sort of request in Sitecore after a certain amount of time.
I first began tinkering with the idea of using the last activity date/time of the logged in user — this is available as a DateTime in the user’s MembershipUser instance via the LastActivityDate property.
However — after reading this article — I learned this date and time does not mean what I thought it had meant, and decided to search for another way to ascertain whether a user is idle in Sitecore.
After some digging around, I discovered Sitecore.Web.Authentication.DomainAccessGuard.Sessions in Sitecore.Kernel.dll — this appears to be a collection of sessions in Sitecore — and immediately felt elated as if I had just won the lottery. I decided to put it to use in the following class (code in this class will be invoked via a scheduled task in Sitecore):
using System; using System.Collections.Generic; using System.Web.Security; using Sitecore.Configuration; using Sitecore.Data; using Sitecore.Data.Items; using Sitecore.Diagnostics; using Sitecore.Security.Accounts; using Sitecore.Tasks; using Sitecore.Web.Authentication; namespace Sitecore.Sandbox.Tasks { public class UnlockItemsTask { private static readonly TimeSpan ElapsedTimeWhenIdle = GetElapsedTimeWhenIdle(); public void UnlockIdleUserItems(Item[] items, CommandItem command, ScheduleItem schedule) { if (ElapsedTimeWhenIdle == TimeSpan.Zero) { return; } IEnumerable<Item> lockedItems = GetLockedItems(schedule.Database); foreach (Item lockedItem in lockedItems) { UnlockIfApplicable(lockedItem); } } private static IEnumerable<Item> GetLockedItems(Database database) { Assert.ArgumentNotNull(database, "database"); return database.SelectItems("fast://*[@__lock='%owner=%']"); } private void UnlockIfApplicable(Item item) { Assert.ArgumentNotNull(item, "item"); if (!ShouldUnlockItem(item)) { return; } Unlock(item); } private static bool ShouldUnlockItem(Item item) { Assert.ArgumentNotNull(item, "item"); if(!item.Locking.IsLocked()) { return false; } string owner = item.Locking.GetOwner(); return !IsUserAdmin(owner) && IsUserIdle(owner); } private static bool IsUserAdmin(string username) { Assert.ArgumentNotNullOrEmpty(username, "username"); User user = User.FromName(username, false); Assert.IsNotNull(user, "User must be null due to a wrinkle in the interwebs :-/"); return user.IsAdministrator; } private static bool IsUserIdle(string username) { Assert.ArgumentNotNullOrEmpty(username, "username"); DomainAccessGuard.Session userSession = DomainAccessGuard.Sessions.Find(session => session.UserName == username); if(userSession == null) { return true; } return userSession.LastRequest.Add(ElapsedTimeWhenIdle) <= DateTime.Now; } private void Unlock(Item item) { Assert.ArgumentNotNull(item, "item"); try { string owner = item.Locking.GetOwner(); item.Editing.BeginEdit(); item.Locking.Unlock(); item.Editing.EndEdit(); Log.Info(string.Format("Unlocked {0} - was locked by {1}", item.Paths.Path, owner), this); } catch (Exception ex) { Log.Error(this.ToString(), ex, this); } } private static TimeSpan GetElapsedTimeWhenIdle() { TimeSpan elapsedTimeWhenIdle; if (TimeSpan.TryParse(Settings.GetSetting("UnlockItems.ElapsedTimeWhenIdle"), out elapsedTimeWhenIdle)) { return elapsedTimeWhenIdle; } return TimeSpan.Zero; } } }
Methods in the class above grab all locked items in Sitecore via a fast query, and unlock them if the users of each are not administrators, and are idle — I determine this from an idle threshold value that is stored in a custom setting (see the patch configuration file below) and the last time the user had made any sort of request in Sitecore via his/her DomainAccessGuard.Session instance from Sitecore.Web.Authentication.DomainAccessGuard.Sessions.
If a DomainAccessGuard.Session instance does not exist for the user — it’s null — this means the user’s session had expired, so we should also unlock the item.
I’ve also included code to log which items have been unlocked by the Unlock method — for auditing purposes — and of course log exceptions if any are encountered — we must do all we can to support our support teams by capturing information in log files :).
I then created a patch configuration file to store our idle threshold value — I’ve used one minute here for testing (I can’t sit around all day waiting for items to unlock ;)):
<?xml version="1.0" encoding="utf-8"?> <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <settings> <setting name="UnlockItems.ElapsedTimeWhenIdle" value="00:00:01:00" /> </settings> </sitecore> </configuration>
I then created a task command for the class above in Sitecore:
I then mapped the task command to a scheduled task (to learn about scheduled tasks, see John West’s blog post where he discusses them):
Let’s light the fuse on this, and see what it does.
I logged into Sitecore using one of my test accounts, and locked some items:
I then logged into Sitecore using a different account in a different browser session, and navigated to one of the locked items:
I then walked away, made a cup of coffee, returned, and saw this:
I opened up my latest Sitecore log, and saw the following:
I do want to caution you from running off with this code, and putting it into your Sitecore instance(s) — it is an all or nothing solution (it will unlock items for all non-adminstrators which might invoke some anger in users, and also defeat the purpose of locking items in the first place), so it’s quite important that a business decision is made before using this solution, or one that is similar in nature.
If you have any thoughts on this, please leave a comment.
Unlock Sitecore Users’ Items During Logout
The other day I saw a post in one of the SDN forums asking how one could go about building a solution to unlock items locked by a user when he/she logs out of Sitecore.
What immediately came to mind was building a new processor for the logout pipeline — this pipeline can be found at /configuration/sitecore/processors/logout in your Sitecore instance’s Web.config — but had to research how one would programmatically get all Sitecore items locked by the current user.
After a bit of fishing in Sitecore.Kernel.dll and Sitecore.Client.dll, I found a query in Sitecore.Client.dll that will give me all locked items for the current user:
Now all we need to do is add it into a custom logout pipeline processor:
using System; using System.Collections.Generic; using System.Linq; using Sitecore.Data.Items; using Sitecore.Diagnostics; using Sitecore.Pipelines.Logout; namespace Sitecore.Sandbox.Pipelines.Logout { public class UnlockMyItems { public void Process(LogoutArgs args) { Assert.ArgumentNotNull(args, "args"); UnlockMyItemsIfAny(); } private void UnlockMyItemsIfAny() { IEnumerable<Item> lockedItems = GetMyLockedItems(); if (!CanProcess(lockedItems)) { return; } foreach (Item lockedItem in lockedItems) { Unlock(lockedItem); } } private static IEnumerable<Item> GetMyLockedItems() { return Context.ContentDatabase.SelectItems(GetMyLockedItemsQuery()); } private static string GetMyLockedItemsQuery() { return string.Format("fast://*[@__lock='%\"{0}\"%']", Context.User.Name); } private static bool CanProcess(IEnumerable<Item> lockedItems) { return lockedItems != null && lockedItems.Any() && lockedItems.Select(item => item.Locking.HasLock()).Any(); } private void Unlock(Item item) { Assert.ArgumentNotNull(item, "item"); if (!item.Locking.HasLock()) { return; } try { item.Editing.BeginEdit(); item.Locking.Unlock(); item.Editing.EndEdit(); } catch (Exception ex) { Log.Error(this.ToString(), ex, this); } } } }
The class above grabs all items locked by the current user in the context content database. If none are found, we don’t move forward on processing.
When there are locked items for the current user, the code checks to see if each item is locked before unlocking, just in case some other account unlocks the item before we unlock it — I don’t know what would happen if we try to unlock an item that isn’t locked. If you know, please share in a comment.
I then injected the above pipeline processor into the logout pipeline using the following patch configuration file:
<?xml version="1.0" encoding="utf-8" ?> <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <processors> <logout> <processor patch:after="*[@type='Sitecore.Pipelines.Logout.CheckModified, Sitecore.Kernel']" type="Sitecore.Sandbox.Pipelines.Logout.UnlockMyItems, Sitecore.Sandbox"/> </logout> </processors> </sitecore> </configuration>
Let’s test-drive this.
I first logged into Sitecore using my ‘mike’ account, and chose the Home item to lock:
It is now locked:
In another session, I logged in using another account, and saw that ‘mike’ had locked the Home item:
I switched back to the other session under the ‘mike’ user, and logged out:
When I logged back in, I saw that the Home item was no longer locked:
If you have any thoughts or suggestions on making this better, please share in a comment below.
Enforce Password Expiration in the Sitecore CMS
I recently worked on a project that called for a feature to expire Sitecore users’ passwords after an elapsed period of time since their passwords were last changed.
The idea behind this is to lessen the probability that an attacker will infiltrate a system — or multiple systems if users reuse their passwords across different applications (this is more common than you think) — within an organization by acquiring old database backups containing users’ passwords.
Since I can’t show you what I built for that project, I cooked up another solution — a custom loggingin processor that determines whether a user’s password has expired in Sitecore:
using System; using System.Web.Security; using Sitecore.Diagnostics; using Sitecore.Pipelines.LoggingIn; using Sitecore.Web; namespace Sitecore.Sandbox.Pipelines.LoggingIn { public class CheckPasswordExpiration { private TimeSpan TimeSpanToExpirePassword { get; set; } private string ChangePasswordPageUrl { get; set; } public void Process(LoggingInArgs args) { Assert.ArgumentNotNull(args, "args"); if (!IsEnabled()) { return; } MembershipUser user = GetMembershipUser(args); if (HasPasswordExpired(user)) { WebUtil.Redirect(ChangePasswordPageUrl); } } private bool IsEnabled() { return IsTimeSpanToExpirePasswordSet() && IsChangePasswordPageUrlSet(); } private bool IsTimeSpanToExpirePasswordSet() { return TimeSpanToExpirePassword > default(TimeSpan); } private bool IsChangePasswordPageUrlSet() { return !string.IsNullOrWhiteSpace(ChangePasswordPageUrl); } private static MembershipUser GetMembershipUser(LoggingInArgs args) { Assert.ArgumentNotNull(args, "args"); Assert.ArgumentNotNullOrEmpty(args.Username, "args.Username"); return Membership.GetUser(args.Username, false); } private bool HasPasswordExpired(MembershipUser user) { return user.LastPasswordChangedDate.Add(TimeSpanToExpirePassword) <= DateTime.Now; } } }
The processor above ascertains whether a user’s password has expired by adding a configured timespan — see the configuration file below — to the last date and time the password was changed, and if that date and time summation is in the past — this means the password should have been changed already — then we redirect the user to a change password page (this is configured to be the Change Password page in Sitecore).
I wired up the custom loggingin processor, its timespan on expiring passwords — here I am using 1 minute since I can’t wait around all day 😉 — and set the change password page to be the url of Sitecore’s Change Password page:
<?xml version="1.0" encoding="utf-8"?> <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <processors> <loggingin> <processor mode="on" type="Sitecore.Sandbox.Pipelines.LoggingIn.CheckPasswordExpiration, Sitecore.Sandbox" patch:before="processor[@type='Sitecore.Pipelines.LoggingIn.CheckStartPage, Sitecore.Kernel']"> <!-- Number of days, hours, minutes and seconds after the last password change date to expire passwords --> <TimeSpanToExpirePassword>00:00:01:00</TimeSpanToExpirePassword> <ChangePasswordPageUrl>/sitecore/login/changepassword.aspx</ChangePasswordPageUrl> </processor> </loggingin> </processors> </sitecore> </configuration>
Let’s test this out.
I went to Sitecore’s login page, and entered my username and password on the login form:
I clicked the Login button, and was redirected to the Change Password page as expected:
If you can think of any other security measures that should be added to Sitecore, please share in a comment.
Prevent Sitecore Users from Using Common Dictionary Words in Passwords
Lately, enhancing security measures in Sitecore have been on my mind. One idea that came to mind today was finding a way to prevent password cracking — a scenario where a script tries to ascertain a user’s password by guessing over and over again what a user’s password might be, by supplying common words from a data store, or dictionary in the password textbox on the Sitecore login page.
As a way to prevent users from using common words in their Sitecore passwords, I decided to build a custom System.Web.Security.MembershipProvider — the interface (not a .NET interface but an abstract class) used by Sitecore out of the box for user management. Before we dive into that code, we need a dictionary of some sort.
I decided to use a list of fruits — all for the purposes of keeping this post simple — that I found on a Wikipedia page. People aren’t kidding when they say you can virtually find everything on Wikipedia, and no doubt all content on Wikipedia is authoritative — just ask any university professor. 😉
I copied some of the fruits on that Wikipedia page into a patch include config file — albeit it would make more sense to put these into a database, or perhaps into Sitecore if doing such a thing in a real-world solution. I am not doing this here for the sake of brevity.
<?xml version="1.0" encoding="utf-8"?> <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <dictionaryWords> <word>Apple</word> <word>Apricot</word> <word>Avocado</word> <word>Banana</word> <word>Breadfruit</word> <word>Bilberry</word> <word>Blackberry</word> <word>Blackcurrant</word> <word>Blueberry</word> <word>Currant</word> <word>Cherry</word> <word>Cherimoya</word> <word>Clementine</word> <word>Cloudberry</word> <word>Coconut</word> <word>Date</word> <word>Damson</word> <word>Dragonfruit</word> <word>Durian</word> <word>Eggplant</word> <word>Elderberry</word> <word>Feijoa</word> <word>Fig</word> <word>Gooseberry</word> <word>Grape</word> <word>Grapefruit</word> <word>Guava</word> <word>Huckleberry</word> <word>Honeydew</word> <word>Jackfruit</word> <word>Jettamelon</word> <word>Jambul</word> <word>Jujube</word> <word>Kiwi fruit</word> <word>Kumquat</word> <word>Legume</word> <word>Lemon</word> <word>Lime</word> <word>Loquat</word> <word>Lychee</word> <word>Mandarine</word> <word>Mango</word> <word>Melon</word> </dictionaryWords> </sitecore> </configuration>
I decided to reuse a utility class I built for my post on expanding Standard Values tokens.
using System; using System.Collections.Generic; using System.Linq; using System.Text; using Sitecore.Diagnostics; using Sitecore.Sandbox.Utilities.StringUtilities.Base; using Sitecore.Sandbox.Utilities.StringUtilities.DTO; namespace Sitecore.Sandbox.Utilities.StringUtilities { public class StringSubstringsChecker : SubstringsChecker<string> { private bool IgnoreCase { get; set; } private StringSubstringsChecker(IEnumerable<string> substrings) : this(null, substrings, false) { } private StringSubstringsChecker(IEnumerable<string> substrings, bool ignoreCase) : this(null, substrings, ignoreCase) { } private StringSubstringsChecker(string source, IEnumerable<string> substrings, bool ignoreCase) : base(source) { SetSubstrings(substrings); SetIgnoreCase(ignoreCase); } private void SetSubstrings(IEnumerable<string> substrings) { AssertSubstrings(substrings); Substrings = substrings; } private static void AssertSubstrings(IEnumerable<string> substrings) { Assert.ArgumentNotNull(substrings, "substrings"); Assert.ArgumentCondition(substrings.Any(), "substrings", "substrings must contain as at least one string!"); } private void SetIgnoreCase(bool ignoreCase) { IgnoreCase = ignoreCase; } protected override bool CanDoCheck() { return !string.IsNullOrEmpty(Source); } protected override bool DoCheck() { Assert.ArgumentNotNullOrEmpty(Source, "Source"); foreach (string substring in Substrings) { if(DoesSourceContainSubstring(substring)) { return true; } } return false; } private bool DoesSourceContainSubstring(string substring) { if (IgnoreCase) { return !IsNotFoundIndex(Source.IndexOf(substring, StringComparison.CurrentCultureIgnoreCase)); } return !IsNotFoundIndex(Source.IndexOf(substring)); } private static bool IsNotFoundIndex(int index) { const int notFound = -1; return index == notFound; } public static ISubstringsChecker<string> CreateNewStringSubstringsContainer(IEnumerable<string> substrings) { return new StringSubstringsChecker(substrings); } public static ISubstringsChecker<string> CreateNewStringSubstringsContainer(IEnumerable<string> substrings, bool ignoreCase) { return new StringSubstringsChecker(substrings, ignoreCase); } public static ISubstringsChecker<string> CreateNewStringSubstringsContainer(string source, IEnumerable<string> substrings, bool ignoreCase) { return new StringSubstringsChecker(source, substrings, ignoreCase); } } }
In the version of our “checker” class above, I added the option to have the “checker” ignore case comparisons for the source and substrings.
Next, I created a new System.Web.Security.MembershipProvider subclass where I am utilizing the decorator pattern to decorate methods around changing passwords and creating users.
By default, we are instantiating an instance of the System.Web.Security.SqlMembershipProvider — this is what my local Sitecore sandbox instance is using, in order to get at the ASP.NET Membership tables in the core database.
using System; using System.Collections.Generic; using System.Collections.Specialized; using System.Linq; using System.Text; using System.Web.Security; using Sitecore.Configuration; using Sitecore.Diagnostics; using Sitecore.Security; using Sitecore.Sandbox.Utilities.StringUtilities; using Sitecore.Sandbox.Utilities.StringUtilities.Base; namespace Sitecore.Sandbox.Security.MembershipProviders { public class PreventDictionaryWordPasswordsMembershipProvider : MembershipProvider { private static IEnumerable<string> _DictionaryWords; private static IEnumerable<string> DictionaryWords { get { if (_DictionaryWords == null) { _DictionaryWords = GetDictionaryWords(); } return _DictionaryWords; } } public override string Name { get { return InnerMembershipProvider.Name; } } public override string ApplicationName { get { return InnerMembershipProvider.ApplicationName; } set { InnerMembershipProvider.ApplicationName = value; } } public override bool EnablePasswordReset { get { return InnerMembershipProvider.EnablePasswordReset; } } public override bool EnablePasswordRetrieval { get { return InnerMembershipProvider.EnablePasswordRetrieval; } } public override int MaxInvalidPasswordAttempts { get { return InnerMembershipProvider.MaxInvalidPasswordAttempts; } } public override int MinRequiredNonAlphanumericCharacters { get { return InnerMembershipProvider.MinRequiredNonAlphanumericCharacters; } } public override int MinRequiredPasswordLength { get { return InnerMembershipProvider.MinRequiredPasswordLength; } } public override int PasswordAttemptWindow { get { return InnerMembershipProvider.PasswordAttemptWindow; } } public override MembershipPasswordFormat PasswordFormat { get { return InnerMembershipProvider.PasswordFormat; } } public override string PasswordStrengthRegularExpression { get { return InnerMembershipProvider.PasswordStrengthRegularExpression; } } public override bool RequiresQuestionAndAnswer { get { return InnerMembershipProvider.RequiresQuestionAndAnswer; } } public override bool RequiresUniqueEmail { get { return InnerMembershipProvider.RequiresUniqueEmail; } } private MembershipProvider InnerMembershipProvider { get; set; } private ISubstringsChecker<string> DictionaryWordsSubstringsChecker { get; set; } public PreventDictionaryWordPasswordsMembershipProvider() : this(CreateNewSqlMembershipProvider(), CreateNewDictionaryWordsSubstringsChecker()) { } public PreventDictionaryWordPasswordsMembershipProvider(MembershipProvider innerMembershipProvider, ISubstringsChecker<string> dictionaryWordsSubstringsChecker) { SetInnerMembershipProvider(innerMembershipProvider); SetDictionaryWordsSubstringsChecker(dictionaryWordsSubstringsChecker); } private void SetInnerMembershipProvider(MembershipProvider innerMembershipProvider) { Assert.ArgumentNotNull(innerMembershipProvider, "innerMembershipProvider"); InnerMembershipProvider = innerMembershipProvider; } private void SetDictionaryWordsSubstringsChecker(ISubstringsChecker<string> dictionaryWordsSubstringsChecker) { Assert.ArgumentNotNull(dictionaryWordsSubstringsChecker, "dictionaryWordsSubstringsChecker"); DictionaryWordsSubstringsChecker = dictionaryWordsSubstringsChecker; } private static MembershipProvider CreateNewSqlMembershipProvider() { return new SqlMembershipProvider(); } private static ISubstringsChecker<string> CreateNewDictionaryWordsSubstringsChecker() { return CreateNewStringSubstringsChecker(DictionaryWords); } private static ISubstringsChecker<string> CreateNewStringSubstringsChecker(IEnumerable<string> substrings) { Assert.ArgumentNotNull(substrings, "substrings"); const bool ignoreCase = true; return StringSubstringsChecker.CreateNewStringSubstringsContainer(substrings, ignoreCase); } private static IEnumerable<string> GetDictionaryWords() { return Factory.GetStringSet("dictionaryWords/word"); } public override bool ChangePassword(string username, string oldPassword, string newPassword) { if (DoesPasswordContainDictionaryWord(newPassword)) { return false; } return InnerMembershipProvider.ChangePassword(username, oldPassword, newPassword); } private bool DoesPasswordContainDictionaryWord(string password) { Assert.ArgumentNotNullOrEmpty(password, "password"); DictionaryWordsSubstringsChecker.Source = password; return DictionaryWordsSubstringsChecker.ContainsSubstrings(); } public override bool ChangePasswordQuestionAndAnswer(string username, string password, string newPasswordQuestion, string newPasswordAnswer) { return InnerMembershipProvider.ChangePasswordQuestionAndAnswer(username, password, newPasswordQuestion, newPasswordAnswer); } public override MembershipUser CreateUser(string username, string password, string email, string passwordQuestion, string passwordAnswer, bool isApproved, object providerUserKey, out MembershipCreateStatus status) { if (DoesPasswordContainDictionaryWord(password)) { status = MembershipCreateStatus.InvalidPassword; return null; } return InnerMembershipProvider.CreateUser(username, password, email, passwordQuestion, passwordAnswer, isApproved, providerUserKey, out status); } public override bool DeleteUser(string userName, bool deleteAllRelatedData) { return InnerMembershipProvider.DeleteUser(userName, deleteAllRelatedData); } public override MembershipUserCollection FindUsersByEmail(string emailToMatch, int pageIndex, int pageSize, out int totalRecords) { return InnerMembershipProvider.FindUsersByEmail(emailToMatch, pageIndex, pageSize, out totalRecords); } public override MembershipUserCollection FindUsersByName(string userNameToMatch, int pageIndex, int pageSize, out int totalRecords) { return InnerMembershipProvider.FindUsersByName(userNameToMatch, pageIndex, pageSize, out totalRecords); } public override MembershipUserCollection GetAllUsers(int pageIndex, int pageSize, out int totalRecords) { return InnerMembershipProvider.GetAllUsers(pageIndex, pageSize, out totalRecords); } public override int GetNumberOfUsersOnline() { return InnerMembershipProvider.GetNumberOfUsersOnline(); } public override string GetPassword(string username, string answer) { return InnerMembershipProvider.GetPassword(username, answer); } public override MembershipUser GetUser(object providerUserKey, bool userIsOnline) { return InnerMembershipProvider.GetUser(providerUserKey, userIsOnline); } public override MembershipUser GetUser(string username, bool userIsOnline) { return InnerMembershipProvider.GetUser(username, userIsOnline); } public override string GetUserNameByEmail(string email) { return InnerMembershipProvider.GetUserNameByEmail(email); } public override void Initialize(string name, NameValueCollection config) { InnerMembershipProvider.Initialize(name, config); } public override string ResetPassword(string username, string answer) { return InnerMembershipProvider.ResetPassword(username, answer); } public override bool UnlockUser(string userName) { return InnerMembershipProvider.UnlockUser(userName); } public override void UpdateUser(MembershipUser user) { InnerMembershipProvider.UpdateUser(user); } public override bool ValidateUser(string username, string password) { return InnerMembershipProvider.ValidateUser(username, password); } } }
In our MembershipProvider above, we have decorated the ChangePassword() and CreateUser() methods by employing a helper method to delegate to our DictionaryWordsSubstringsChecker instance — an instance of the StringSubstringsChecker class above — to see if the supplied password contains any of the fruits found in our collection, and prevent the workflow from moving forward in changing a user’s password, or creating a new user if one of the fruits is found in the provided password.
If we don’t find one of the fruits in the password, we then delegate to the inner MembershipProvider instance — this instance takes care of the rest around changing passwords, or creating new users.
I then had to register my MemberProvider in my Web.config — this cannot be placed in a patch include file since it lives outside of the <sitecore></sitecore> element.
<configuration> <membership defaultProvider="sitecore" hashAlgorithmType="SHA1"> <providers> <clear/> <add name="sitecore" type="Sitecore.Security.SitecoreMembershipProvider, Sitecore.Kernel" realProviderName="sql" providerWildcard="%" raiseEvents="true"/> <!-- our new provider --> <add name="sql" type="Sitecore.Sandbox.Security.MembershipProviders.PreventDictionaryWordPasswordsMembershipProvider, Sitecore.Sandbox" connectionStringName="core" applicationName="sitecore" minRequiredPasswordLength="6" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="256"/> <add name="switcher" type="Sitecore.Security.SwitchingMembershipProvider, Sitecore.Kernel" applicationName="sitecore" mappings="switchingProviders/membership"/> </providers> </membership> </configuration>
So, let’s see what the code above does.
I first tried to create a new user with a password containing a fruit.
I then used a fruit that was not in the collection of fruits above, and successfully created my new user.
Next, I tried to change an existing user’s password to one that contains the word “apple”.
I successfully changed this same user’s password using the word orange — it does not live in our collection of fruits above.
And that’s all there is to it. If you can think of alternative ways of doing this, or additional security features to implement, please drop a comment.
Until next time, have a Sitecoretastic day!