This post describes a simple claims helper block I put together. This block can come in useful if you are using federated authentication and would like to inspect all claims for the current user.
I created this whilst developing the solution for implementing federated security in EPiServer using Auth0.
In my previous post I described how its possible to implement federated security in EPiServer using Auth0. However the steps described on allow users to log into your site with Auth0. It's not possible to log into the EPiServer UI using the described steps. The post describes how to extend the implementation to allow users logging in via Auth0 to use the EPiServer UI.
This is due to the fact that when using federated security EPiServer respects the http://schemas.microsoft.com/ws/2008/06/identity/claims/role claim to check access rights. However many providers do not issue these claims so we need an Auth0 rule to create some roles then do a little work in EPiServer to map them into http://schemas.microsoft.com/ws/2008/06/identity/claims/role claims.
This post describes how to allow federated security in EPiServer using Auth0. Auth0 is an identity broker that's extensible, enterprise class and reduces the friction between identity infrastructure and developers. I'm not affiliated with Auth0 in any way so this post is written from my own (admittedly very good) experience with Auth0. The post contains a number of step by step instructions and is intended to be an example on how to use Auth0 with EPiServer. The original demo was presented in November 2014 at the EPiServer UK customer and partner day.
The new EPiServer UI introduced with EPiServer 7 gave users a sleek new interface that's easy to use and simple to navigate. All unnecessary UI elements are hidden away until you need them. When users need them frequently areas can be pinned out. However the top menu cannot be pinned out and always hides itself. Some power users find themselves moving between several top menu items at a time such as between edit mode and Visitor Groups. The pull down menu at the top of the page takes precious milliseconds to find and click. For power users every millisecond counts right ;)?
So I quickly put a "MenuPin" add-on together that allows users to pin the menu at the top of the EPiServer UI. This works for edit mode only at this point. The pin works the same as pinning the gadget areas in the editor UI:
In a previous post I introduced Virtual Template System for EPiServer. This post is a quick introduction on how to use the UI.
When you first open Virtual Template System by clicking Virtual Templates, then Edit you will be presented with a list of templates that are in the repository. As this is the first time you've used it the list will be empty. Clicking the "Show all templates (including those on disk)" option will list out all templates that are on disk, plus those already in the repository. By default it looks for cshtml, CSS and js within the application.
Quite simply Virtual Template System for EPiServer allows users to view and modify templates from the EPiServer UI. Why would you do this? The internet is a fast moving world and our customers and clients are demanding. They may not want to wait for a full release to update a template and shouldn't really need to if it's only for a couple of lines of mark up or CSS to be changed. Virtual Template System tries to help this issue by allowing users to make templates visible and editable from the EPiServer UI.
One of the most exciting features in EPiServer Commerce 7.5 (for me) is MetaClass and MetaField mapping from code to the Catalog system in EPiServer Commerce. In short this allows you to create/edit/access MetaClass and MetaFields in EPiServer Commerce 7.5 through code in the same way you can for any other content type in EPiServer.