Post reply

SSRS Reporting Server 2019 CustomSecurity extension issue

  • February 24, 2023 at 8:05 am

    #4153610

    In Microsoft SQL 2016 SSRS, in a CustomSecurity extension, this GetUserInfo method is invoked and HttpContext.Current.User contains data:

    public void GetUserInfo(out IIdentity userIdentity, out IntPtr userId)  
    {  
       // If the current user identity is not null,  
       // set the userIdentity parameter to that of the current user   
       if (HttpContext.Current != null  
           && HttpContext.Current.User != null)  
       {  
           userIdentity = HttpContext.Current.User.Identity;  
       }  
       else  
          userIdentity = null;  
       // initialize a pointer to the current user id to zero  
       userId = IntPtr.Zero;  
    }

    image1

    But in Microsoft SQL 2019 SSRS, in the same CustomSecurity extension, another GetUserInfo method (IAuthenticationExtension2) is invoked (by the same method in the client application that sends requests to this CustomSecurity extension) and HttpContext.Current and requestContext.User don’t contain data:

    public void GetUserInfo(IRSRequestContext requestContext, out IIdentity userIdentity, out IntPtr userId)
    {
        userIdentity = null;
        if (requestContext.User != null)
        {
            userIdentity = requestContext.User;
        }
        // initialize a pointer to the current user id to zero
        userId = IntPtr.Zero;
    }

    image2

    Why are HttpContext.Current and requestContext.User null in Microsoft SQL 2019 SSRS CustomSecurity extension? And how can we get userIdentity there in this case?

  • February 25, 2023 at 8:10 am

    #4154010

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply