Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Verified Answer
  • Replies replies
    9
  • Subscribers subscribers
    14
  • Views views
    775
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Network Admin can not upload file

shanedriggs
 

We have a network admin that can not upload via FILR to a Net Folder. He has full rights rights to the folder in AD. We have given him rights in FILR. What could cause this?

The only thing I can think is, he is part of two AD groups. One group restricts his ability to to right to the folder. The admin group he is part of, gives him full access to the folder. Could this be causing the issue?

Thanks

Shane

Parents
  • 0  

    If you are talking about the admin user, they use the proxy user account to access files.

    If you are talking about an LDAP user are the groups used to asign rights imported into Filr?

  • Verified Answer

    +1   in reply to   

    OK, I have the solution. The current AD domain was created a few years ago when they merged 14 different domains into one. After the migration the d3admins group had a new SID with the new domain. But it also had its old SID in the sidhistory. The CIFS server was using the d3admins sid from the sidhistory. Mapped drives worked, because the workstation also referenced the sidhistory to match the group d3admins. But FILR is only looking at the objectSid to reference the group D3admins. For now we will use a new group, so it will have a SID FILR will be able to reference. I have opened a ticket to see if we can get FILR to also look at the SIDHistory when referencing users and groups.

Reply

  • Verified Answer

    +1   in reply to   

    OK, I have the solution. The current AD domain was created a few years ago when they merged 14 different domains into one. After the migration the d3admins group had a new SID with the new domain. But it also had its old SID in the sidhistory. The CIFS server was using the d3admins sid from the sidhistory. Mapped drives worked, because the workstation also referenced the sidhistory to match the group d3admins. But FILR is only looking at the objectSid to reference the group D3admins. For now we will use a new group, so it will have a SID FILR will be able to reference. I have opened a ticket to see if we can get FILR to also look at the SIDHistory when referencing users and groups.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.