Hi Gunnar,

Did you get anywhere with this? I am trying to check if a back office user is currently logged in to the back office in a INotificationHandler<RoutingRequestNotification>, however this code always returns null:

var user = _backOfficeSecurityAccessor.Value.BackOfficeSecurity.CurrentUser;

CurrentUser is always null.

I've got the same problem using the IBackOfficeSecurity:

var user = backOfficeSecurity.CurrentUser;

CurrentUser is always null...

Do you mean from one of the public websites razor views, you want to know if the person viewing the page is currently a backoffice user logged into the backoffice?

If so, you might need to authorize the request using the backoffice authentication scheme. This doesn't happen out-of-the box, I don't think.

Shooting from the hip here, but maybe something like this will work?

• Override the default rendering controller, so you can decorate it with the authorize attribute:

.

[Authorize(AuthenticationSchemes = Umbraco.Cms.Core.Constants.Security.BackOfficeAuthenticationType)]
[AllowAnonymous]
public class CustomRenderController : RenderController
{
    public CustomRenderController(ILogger<RenderController> logger, ICompositeViewEngine compositeViewEngine, IUmbracoContextAccessor umbracoContextAccessor)
        : base(logger, compositeViewEngine, umbracoContextAccessor)
    {
    }
}

• register it in startup.cs:

      services.Configure<UmbracoRenderingDefaultsOptions>(c =>
      {
          c.DefaultControllerType = typeof(CustomRenderController);
      });
  

This will try authorize the request with the backoffice scheme, but because we have "AllowAnonymous" it wont force the user to login.

• In the razor view, you can use:

  var isLoggedIn = Context.User?.Identity?.IsAuthenticated ?? false;
  

Hmm. This might only be able to work if you are not also using member login.

Hi Gunnar 👋

I am curious as to what you are trying to achieve by wanting the logged in back office to be available on the front end of the site.

As with anything in code depending on what your trying to do, there may be one or more ways to how to solve the problem.

Warren

Edit: I took this from Umbracos own preview code...

Well, here's what I ended up doing in my Middleware:

private void AddBackofficeIdentityIfAvailable(HttpContext context)
    {
        var cookieOptions = context.RequestServices.GetRequiredService<IOptionsSnapshot<CookieAuthenticationOptions>>()
            .Get(Umbraco.Cms.Core.Constants.Security.BackOfficeAuthenticationType);

        if (cookieOptions == null)
        {
            throw new InvalidOperationException("No cookie options found with name " + Umbraco.Cms.Core.Constants.Security.BackOfficeAuthenticationType);
        }

        if (context.Request.Cookies.TryGetValue(cookieOptions.Cookie.Name, out var cookie))
        {
            var unprotected = cookieOptions.TicketDataFormat.Unprotect(cookie);
            var backOfficeIdentity = unprotected?.Principal.GetUmbracoIdentity();
            if (backOfficeIdentity != null)
            {
                // Ok, we've got a real ticket, now we can add this ticket's identity to the current
                // Principal, this means we'll have 2 identities assigned to the principal which we can
                // use to authorize and allow for a back office User.
                context.User.AddIdentity(backOfficeIdentity);
            }
        }
    }

Then I tried getting the backOfficeIdentity liks this:

var backOfficeIdentity = context.User.Identities.FirstOrDefault(c => c.AuthenticationType == Umbraco.Cms.Core.Constants.Security.BackOfficeAuthenticationType);

And finally you can check if it's ok and authenticated with

backOfficeIdentity != null && backOfficeIdentity.IsAuthenticated

OK I got a reply internally as was suggested a similar code sample as MatsStam, that might also help you.

public class DemoController : Controller
{
    private readonly IOptionsSnapshot<CookieAuthenticationOptions> _snapshot;

    public DemoController(IOptionsSnapshot<CookieAuthenticationOptions> snapshot)
    {
        _snapshot = snapshot;
    }

    [HttpGet("demo")]
    public async Task<IActionResult> Demo()
    {
        CookieAuthenticationOptions cookieOptions = _snapshot.Get(Core.Constants.Security.BackOfficeAuthenticationType);

        string backOfficeCookie = HttpContext.Request.Cookies[cookieOptions.Cookie.Name!];
        AuthenticationTicket unprotected = cookieOptions.TicketDataFormat.Unprotect(backOfficeCookie!);
        ClaimsIdentity backOfficeIdentity = unprotected!.Principal.GetUmbracoIdentity();

        return Ok(backOfficeIdentity.Name);
    }
}

Hey Warren, I am trying to determine if a backoffice user is logged in and possibly what groups the user belongs to outside of backoffice routed requests.

It does look like your recent code examples provide the required information, thank you MatsStam and Warren for taking the time.

Will mark as answered to help others despite not having had a chance to test myself, thanks all

Hi Marcus, thank you so much for sharing your solution. I cannot make it work in Razor-view. Can you advice me how to check (in Razor) if the user is logged in to Backoffice, when using your "IBackofficeUserAccessor"-implementation?

I am trying something like this: var LoggedIn = new BackofficeUserAccessor().BackofficeUser;

This way I have checked in Umbraco 8 earlier: var ticket = new System.Web.HttpContextWrapper(System.Web.HttpContext.Current).GetUmbracoAuthTicket();

Thanks again Marcus. /Best regards Peter

Hi There is a community package called Our.Umbraco.TagHelpers.

https://www.nuget.org/packages/Our.Umbraco.TagHelpers/

I used Markus’ code to enable me to create a tag helper which renders an edit link on the front end of the user is logged into Umbraco.

Our next move is to create a tag helper for only showing content if the user is logged into Umbraco. I think it will probably be added this week or next.

It will probably work like this:

If the user is not logged into Umbraco then the div and its contents won’t be rendered.

Paul

Hi Mats, Thanks a lot. It worked. Here is my solution:

1. make a new class file in the root of your project and name it "BackofficeUserAccessor.cs" and copy Marcus code suggestion into the file (see above)

2. open your startup.cs file and insert the following into the ConfigureServices method:

services.AddTransient<IBackofficeUserAccessor, BackofficeUserAccessor>();

1. open your Razor-view / cshtml-file

   • Insert the following in the top:

   @inject IBackofficeUserAccessor _backofficeUserAccessor

   • insert the following to check if the user is logged into Umbraco backoffice:

var IsAdmin = _backofficeUserAccessor.BackofficeUser.IsAuthenticated;

if (IsAdmin == true) { EDIT Page }

Paul :) I tried to work with the Taghelper and got it to work. In my case I think it is a little overkill to use a taghelper for checking this, when you can use a simple if-statement. Once again I really appreciate your feedback. Feel free to contact me if you need more info...

Here is the example with the tag-helper:

<AdminLogin condition="IsAdmin == true"><a href="/umbraco#/content/content/edit/@Model.Id">EDIT Page</a></AdminLogin>

Best regards Peter

hello - Ive just come across this thread and like Peter Dyhrberg i am looking for a way of determing if there is currently a backoffice user logged in so that on the website frontend a convenient edit link can be provided to the respective content in the CMS. Is this still a case of rolling your own or is there something in 9.2 or forthcoming in 9.3 that helps with this? thanks

is working on a reply...