Viya Experts,   can we block the access to /identities/users and /identities/groups without breaking the applications in sas viya ? every authenticated user can list all users and groups in our environment. Or maybe even better are there hardening advices on the rules in sas viya.   Regards,   Dik ... View more

Dear community experts. I have an issue with inodes in our backups , especially postgres . wc -l gives me 642258  642258 .........../20250507-010211F/__default__/postgres/SharedServices_pg_dump.dmp/blobs.toc The issue is that it looks that there are orphaned largeobjects. I suspect the export and import of reports.  Daily we export and import our reports.  We delete the old ones, but it looks like this does not correctly delete the large objects. We use 'sas-viya transfer export  ' and 'sas-viya transfer delete'. sh-4.4$ vacuumlo -n SharedServices Connected to database "SharedServices" Test run: no large objects will be removed! Checking content_data_oid_no in files.file_content Checking content_bin in transfer.large_object Checking content_bin in transfer.map_object Checking object_content_txt in transfer.package_object Checking object_summary_txt in transfer.package_object Checking error_txt in transfer.transfer_export_job Checking request_txt in transfer.transfer_export_job Checking error_txt in transfer.transfer_export_task Checking error_txt in transfer.transfer_import_job Checking request_txt in transfer.transfer_import_job Checking error_txt in transfer.transfer_import_task Checking model_xml_doc_oid in workflow.wf_definition_model Checking message_json_doc_oid in workflow.wf_history_event Would remove 447798 large objects from database "SharedServices".   Do we have to run : vacuumlo SharedServices on a regular schedule ? Is this normal behavior of 'sas-viya transfer' ? Regards   Dik.   ... View more