mfeinman62 asked a question.
Hi all ...
One of the items I am looking into is the reassignment of private views or reports from a Windows Authentication id (Domain/Username) to a SAML-based id (E-mail Address). In other words, after the conversion from Windows Authentication to SAML Authentication, I want MyDomain/JohnDoe to still access his private reports and views after his persona becomes JohnDoe@MyDomain.com.
After doing some research, I see that I can reassign the reports two ways:
- I can modify the FNMSCompliance.dbo.ComplianceSavedSearch table and set the private report to public (set RestrictedAccessTypeID = 1) but that makes it available to everyone. Not an issue if I get permission to do this.
- I can modify the FNMSCompliance.dbo.ComplianceSavedSearch table and update the ownership id (set CreatedByOperatorID to the ComplianceOperatorID of the new owner).
[I may have to make a private folder public (or change the folder to one that already exists).]
While writing these queries and the SQL update statement, I saw that there are private reports and views that exist for employees who no longer work at my agency. Some date back many years.
I could reassign them to someone else or make them public, but that got me thinking - is there a way to clean up private reports/views owned by ex-users?
--Mark
The field CreatedByOperatorID in ComplianceSavedSearch is actually a foreign key to ComplianceOperator. I couldn't find any example for reports with limited access and a CreatedByOperatorID missing, I assume the removal of an operator also removes personal reports.
There might still be disable operators with private views and/or reports.
SELECT
css.ComplianceSavedSearchID
,css.SearchName
,co.OperatorLogin
,IsEnabled
FROM ComplianceSavedSearch css
LEFT JOIN ComplianceOperator co
ON css.CreatedByOperatorID = co.ComplianceOperatorID
WHERE css.RestrictedAccessTypeID = 2
AND co.IsEnabled = 0