Un Lock Sitecore admin account

There are times when you
- Upgrade Sitecore locally
- Restore databases in your local Sitecore instance.

And you are no longer able to login to the Sitecore admin interface with the default admin username and password b.

When this happens you can unlock the Sitecore admin account and reset the password back to b.

To do this copy this aspx file to your Website\sitecore\admin folder (and overwrite existing file)

Next make sure your local web.config (in the root Website) folder has the following settings
minRequiredPasswordLength="1"
minRequiredNonalphanumericCharacters="0"

Lastly go to the following page
https://YourSitecore.com/sitecore/admin/unlock_admin.aspx

And click the Unlock Administrator button.
That's it, you can now login to your local Sitecore instance.

6-6-2022 Update:

If you are not able to get to the unlock_admin.aspx page as newer Sitecore versions have a separate identity server, I found the following way to unlock a local account.

I will assume that you have access to the local SQL server databases. Go to the database website_Core and open the table dbo.aspnet_membership. In this table look for the rows that have the column "IsLockedOut" = 1. Also look for the "Comment" Column and it should say "Sitecore Administrator". Just Set IsLockedOut=False and you should be good.

Happy Sitecoreing!

Comments

Local setup of a SSL certificate

Creating a local ssl certificate is easy. You can do so by creating a self signed certificate in IIS and assigning that to you local site. However you may notice that with newer TLS 1.2 standard, tools like TDS (Team Development for Sitecore) and others stop working and complain about local certificates with errors like Exception: System.Security.Authentication.AuthenticationException Message: The remote certificate is invalid according to the validation procedure. To fix this issue, these were the steps I followed. Hope this helps others that are facing similar issues. 1. Run the following Powershell command to create a local self signed cert (replace xxx.local.com with your local dns): New-SelfSignedCertificate -CertStoreLocation Cert:\LocalMachine\My -DnsName "xxx.local.com" -FriendlyName "xxx.local.com" -NotAfter (Get-Date).AddYears(10) 2. Win Key + search for "Manage computer certificates". Make sure your certificate is in the following 3

Sitecore clear cache setting

Sitecore has extensive cache settings. You can add caching at the rendering level so it affects all instances of that rendering. Or you can add caching at the component level on a particular page via the presentation details. This is all good when you are setting it up, but once this goes to production, the way caching is supposed to work is that the cache should get cleared after an item is published. So after an item is published, any associated cache should also automatically get updated. In our case, we saw that once we went to production (with extensive caching enabled) our pages loaded much faster. However when the content authors were updating content, the updates were not making it to the delivery servers. The content seemed to be stuck in the cache. We noticed that we had to do one of the following to see the updated cache. Go to the admin cache page [SitecoreSite/sitecore/admin/Cache.aspx] and click the "Clear all" button. This is not viable long term solution

Using Okta Authentication for a Sitecore client site

I recently had a project where we had to add a new Sitecore site to an already multi site Sitecore 8.2 Update 7 instance. This new site had to integrate with Okta to manage user authentication. I found many articles online that integrated Okta and Sitecore's admin interface but I could not find one that just integrated Okta with a client Sitecore site. My first step was to use Okta's available ASP.NET MVC projects on their Dev site and test them out. This worked very well with the first Authenticated method I tried which was WS-Fed. But when I tried to use the same authentication method with a site in Sitecore I got errors in my logs like the following: Sitecore.Security.Principal.SitecoreIdentity does not contain a definition for Claims Claims are available in HttpContext.User.Identity but not in Sitecore.Security.Principal.SitecoreIdentity, and since we are using a Sitecore site we could not read the claims. I tried to make claims work in Sitecore using various online a

SITECOREing

Search This Blog