SAP Security Blog
Browsing Year
See SAP Note 2745697 – CX_HRPA_INVALID_INFOTYPE_DB happens when deleting a user from SU01. Run report RPUPAV00 for personnel number (get this value from dump) first and then delete the user
PostgreSQL version 10 or 11 are not supported yet. Only PostgreSQL 8 and 9 are supported in SAP PD 16.6. There is currently no target SAP PD Service Pack scheduled for the new feature request CR 816576. It is being reviewed by Product Group. Please mark this KBA as a Favorite to be automatically notified when this enhancement is implemented.
See SAP OSS 727139/2020 for details. I’m proud to inform that SAP has finally released a fix for this problem : 2990918 – DBA Cockpit: SAP Screen Personas in DBA Cockpit not supported. How to fix constant spinning cursor: execute report RSDBAFORCEACCEXPLAIN to reset Java-based and HTML5-based query plan display back to generic ALV tree-based …
SAP Note 1000004 – Merging and optimizing analysis authorizations SAP Note 2291805 – RS2HANA_AUTH089 – “Char. XXX is auth. relevant, but missing in authorization object” when generating HANA-View authorizations A workaround in RSECADMIN : for a characteristic that fails in BW Analysis Authorization object (see S_RS_AUTH) from concerned role try to maintain value ‘I EQ …
Pre-requisite: access to SAP Learning Hub is required. What’s in it for you: TECHED_SEC367 | Authentication, SSO, and Authorization Best Practices in Hybrid Landscapes (SAP TechEd) SUP_VBP_1000 | Setup SAP Cloud Platform Security TECHED_SEC362 | Hands-On Introduction to Data Masking and Anonymization Using SAP HANA (SAP TechEd) TECHED_SEC303 | Achieve a Secure Architecture Using SAP …
This repository contains code that can be used to automatically deploy SAP landscapes in the Azure Cloud: https://github.com/Azure/sap-hana
SAP Note 2600030 – Parameter Recommendations in SAP HANA Environments
Transaction SE16N_EMERGENCY requires transaction SM01_CUS, which is available only with SAP_BASIS 750.
Sometimes passwords are required for technical communications between system components. In this case it is highly recommended to use the user type “B – SYSTEM” (see SAP note 622464 and SAP note 1023437 for background information)
Blog: https://www.daniel-berlin.de/security/sap-sec/password-hash-algorithms/ SAP Note 1458262 – ABAP: recommended settings for password hash algorithms SAP Note 1484692 – Protect read access to password hash value tables SAP Note 2845609 – How to find user name with legacy hash values when executing report CLEANUP_PASSWORD_HASH_VALUES