inetpub wwwroot inherited permissions for PasswordVault web application

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

inetpub wwwroot inherited permissions for PasswordVault web application

L2 Linker

Hi,

 

Installation training notes 'recommended to accept default folder in order to inherit permissions correctly'.

 

May seem pedantic, however 'inherit permissions' would mean in my mind a simply inheritance - 'inherit permissions *correctly* indicates there may be some shenanigans under the hood.

 

I have inherited a deployment where PasswordVault web application has been redirected to another drive, however the Default Website remains under C:\inetpub\wwwroot.

 

Looking at my lab install (where default drive was left as is during install), I can see IISUSERS has inherited from wwwroot, and all others from inetpub. Not easy to see all advanced/special permissions however.

 

Question...: Is there any *easy* way to manually rectify this so all permissions are as they should be, or is it the case that I will need to manually review and copy each of the permission settings from the original C:\inetpub and C:\inetpub\wwwroot locations?

 

Worth noting that on the system where PasswordVault is in a different directory, that the solution does still seem to be working - not sure how it may impact any future upgrades, however...

 

I appreciate the above is a little waffly - happy to expand on anything if needed.

 

Image is from my lab host. On customer host, all permissions have been inherited from root drive.

 

068Ht00000Vblt8IAB.jpg 

Many thanks,

3 REPLIES 3

L7 Applicator

Hi @Darren Mease​ 

 

You can apply these permissions via domain GPO if you don't want to manually correct it. But yes while creating the GPO for the first time, you will need to correct and then apply the permissions.

 

https://docs.cyberark.com/pam-self-hosted/Latest/en/Content/PAS%20INST/PVWA-install-post-installation.htm

L2 Linker

Cheers Malhar,

 

Sorry if I am missing anything - I am familiar with the documentation, however it covers the permissions under <INSTALL>\CyberArk\Password Vault Web Access, and not the permissions required under inetpub?

 

I am guessing that this is due to the fact that in majority of cases people will accept default install path.

 

I will look to manually configure the permissions to reflect those configured under the main inetpub\ and inetpub\wwwroot\ paths.

 

cheers,

L2 Linker

Hi,

 

Sanity check: Assuming that installation wizard is used, and assuming that only drive is changed for inetpub directory, I am guessing that the below should suffice on future builds:

 

- <run PVWA_Prerequisites.ps1 as per standard process>

- IIS > Default Web Site > Advanced Settings

- Physical Path: Update to reflect new location

- <run PVWA install wizard, setting web application target as applicable>

 

If the above is followed, it *may* be the case that the permissions are copied - may need to be tested?

 

Does the above seem reasonable?

 

Note that in both 13.2 and 14.0 documentation, in the PVWA Installation section (install wizard, web application destination), it notes that an alternative destination can be browsed to *but* there is no warning regarding permission inheritance.

 

cheers,

  • 156 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!