I am seeing same issue when trying to migrate from 6.3 to 6.5. Do we know the fix for this issue?

CauseExtra SDI config needed for /conf folder.Solution* Add extra configuration for /conf folder.* Add "ModMimeUsePathInfo On" to the VirtualHost in Apache so includes get processed on the first request.

ALindley: I was able to make it work on SSO enabled portal. There are 2 things that needs to be done in order to achieve this:1. Set sling:sudo cookie with the user name that you want to impersonate as.2. On Server side, using user admin or any service user that has priviledge on /home/users, set the rep:impersonator property as current user on the user that you are trying to impersonate as.

@Jörg Hohb :Also current logged in user is canImpersonate and I want to setup the impersonation property on jrUser. canImpersonate is a member of user-adminsitrations which means this user has all the rights to update user/groups.Thanks,Rajeev

@Jörg HohThank you for the details. Does jrUser needs any specific permissions in repository in order to successfully grant impersonation right to canImpersonate?

smacdonald2008​: Below are the 3 options that we tried:Scenario 1:Boolean checkImpersonated = userB.getImpersonation().grantImpersonation(userA.getPrincipal());//always returns false.Scenario 2:Value userAuthorizableId=session.getValueFactory().createValue(userSession.getUserID(), PropertyType.STRING);User userB=(User) userManager.getAuthorizable(impersonateUser);userB.setProperty("rep:impersonators", impersonator);sessionScenario 3:String impersonators = {“user1@test.com”,”test2@test.com”};Auth...

Hi gauravd83019631​ : It is working for unlocked components which are authored on the pages. Issue is with locked components. Where can we find the system user used by SDI?

We can't unlock the component as it is the header/ footer for template. These needs to be fixed on template and authors should not be able to change it on individual pages.

I am also facing issue with locked component in editable template. Setting SDI on it is not working. I even tried an osgi configuration for template path with resource type of the locked resource. Do we have any solution for this issue?Thanks,Rajeev