SFTP destination - file permissions at the destination

[Former Member]

• Our BO setup runs SAP BO 4.2 SP3 and we had recently configured some reports to go to a sftp destination thru scheduling. We are able to successfully specify the properties and fingerprint and are able to send the file to the destination site. However, the files that get written on the destination linux server have only read and write permissions for the user and no permissions set for the group. The umask is not the issue at the destination side; the file appears restricted when it originated from BO application and so the umask is not preventing the group read permissions. I would like to know what file permissions are set to the report by BO before being sent thru sftp to destination and if there are any ways to specify or change those permissions. I will appreciate any details or pointers in this regard.

[denis_konovalov]

I doubt that the permissions are set by BO. We usually do not do anything like that and permissions are assumed from the OS/Folder/User which runs the process.
In this case BOE scheduling process (user A) sends the file to SFTP server, it is the SFTP server that saves the file in the specified location.
So the user under which SFTP is running (User B) should be the responsible party for the file when it is written.

[Former Member]

Thanks so much for your response!! To also test the scenario in a different way, from the same BO app server (Windows), I used Putty SFTP (outside of BO) to log in to the same sftp destination and wrote a test file to the same directory as the same user. Now, I'm able to see read permissions for group as per the settings on the destination side. However, the files sent from BO to the same server and directory as the same user lost the group permissions. Could you share your thoughts?

[denis_konovalov]

Did you login to the BOE server OS as the user which runs BOE SIA ?
Did you used the same SFTP user ?
If those yes - time to investigate :), contact SAP support , BI-BIP-ADM component. Something is a miss here.

p.s.
I still believe that BOE doesn't set file permissions.

[Former Member]

The SIA is running as LocalSystem user and I'm logged in with different user with administrator access and ran Putty sftp as administrator. I used the same SFTP user in Putty SFTP and wrote to the same directory as the BO application did.

[denis_konovalov]

AHA !!!!

run SIA using admin user - see what happens.

[Former Member]

Just an update so far- I see the default to running SIA is as LocalSystem user which has extended privileges and I'm unable to run it as a different user. I'll check and get back to you on this. Do you think the SIA user could impact the file permissions that the sftp'ed file end up with at the destination?

[denis_konovalov]

Think about how the file permissions work on Win and Unix - there is no equivalent of localsystem account in unix, so the permissions that user has on files are not exactly translatable to unix...
In this workflow - the SFTP server receives the file owned by this account. So it makes sense that's where those weird permissions came from.