Skip to main content

Sitecore IP Geolocation

 To setup Sitecore IP Geolocation functionality, you must go to the Sitecore Support & Self Service portal and sign up for a subscription. Refer to this Sitecore article for more info. 

After we have subscribed to the Sitecore IP Geolocation functionality to validate it we use the TestIP.aspx page. Check out thie Sitecore support page to get the TestIP.aspx page and upload it to the Sitecore folder on your server. Open the https://hostname/sitecore/TestIp.aspx page

Sample Test IP's to test with: 

Africa IP : 102.129.96.0
US IP: 69.162.81.155
UK IP: 101.167.212.0

Make sure the response from the TestIP.spx has the correct country for different test IP's.

Once this works we know that the Sitecore IP Geolocation functionality is enabled. 

How do we use this functionality in our application. 
  1. Just use the personalization rules in Sitecore under the "Geo IP" section (see image below) . So you can control what content is shown to a user based on their location. 
  2. We can write custom code that uses the Geo IP Info. More info about this is in the sample code below. 



Comments

Popular posts from this blog

Sitecore: Get list of logged in users

I had a deployment today and wanted to find a list of users who were logged into the Sitecore admin site. This was mainly so that I can contact them and let them know that a deployment was going to happen. I found the following link very useful as it gave me exactly what I was looking for. A list of users that were logged in and I contacted them. It also has the ability to Kick off users! http://{YourWebsite}/sitecore/client/Applications/LicenseOptions/KickUser Note: You can only see other users in this list if you have the right administrator permission. Logging in with a lower access level user only gave me the logged in user and no one else on the list.

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