HA 240 Authorization
HA 240 Authorization
HA 240 Authorization
Unit 1 Lesson 1
Authorzation – users in system who should only see and do what they need to fulfill
Audito Logging
Indexserver.ini
- In HANA Cockpit or Security Editor of SAP HANA Studio for Password Policies
- JDBC/ODBC
- HTTP for XS Applications
- Connections support standard SQL with SAP HANA Specific extentions
In Detail
- SQL Privileges – access data and operations on database objects (tables, views)
- Analytic Privileges – analytic views, see row-level access
- Application Privileges – start and execute applications XS
- System Privileges – administer actions, Backup, user management
Connection Types
- Client to Server
- Internal Connection (within HANA Components) (ex. Notes of Scale Out System)
- Connections between Data Center ( DR, Sys Replication)
DB Encryption
Security Administration
- HANA Studio – central development, main admin tool HANA
- SAP SOlutons Manager – management of SAP Landscape
- HANA WebIDE – development environment for HANA
- HANA Cockpit – monitoring of individual HANA SYs
- DB Control Center – Lanscape Monitoring for SAP DB
Hierarchy of Packages
Type of Objects
Activation
DEFINIER MODE
- Authorization check is run against privilages of the user who created the object, not user
accessing the object
INVOKER MODE
- authorization check is run against the pivilage of the accessing user
Steps:
Repository Role
- Advantages: Grantor doesn’t need the privilege to Grant, TRANSPORTABLE, can de-couple
creation of role from ownership and granting
- Can be created using runtime objects that follow SQL Principles
- Compared to Catalog Roles, Advantages are
o Versioning
o Integration
o Standard Transport Mechanisms
o Decoupling of Role Creation from role granting or revoking
o Support Transport Cycle DEV QA PROD
Role Management
JDBC/ODBC Access
Restricted Users
Internal DB users
- Not real people, used for admin tasks such as creating objects and granting privilages
- SYS and SYS Repo Technical users
Database Users
- SYSTEM – used for creating other database users, access system tables, recommended to access
before starting Operation
- SID ADMIN – OS administrator, unlimited access to all local resources, user at operating system
level
- SYS – internal DB user, owner of database objects such as system tables and monitoring views
- SYS REPO – used by HANA Repository, consist of packages that contain design time version of
various objects (calculation views, procedures, analytic privilages
- SYS Statistics – internal monitoring of HANA DB
HANA Cockpit
Schema – location of catalog objects, not all schemas have a DB account and can be owned by any
account
Password Policies – rules or a password policy, can be changed in HANA Studio or Security WebIDE
Password Blacklist – list of words not allowed to be used as passwords or past passwords
- Do all computation and processing in the HANA Server and return results to Application Services
- Application logic processing is done on the database. No need for traditional application server =
reduced cost of ownership
- Single development landscape. Less risk of inconsistencies
- Speed of development is fast with web-based data access.
SQLCC Scenario
Vision of XS Advanced
- Create interface to BW Data using HANA Views (Calculation views) and Dynamic Analytic
Privilages used by native HANA Clients and applications
- Authorization in HANA are required for users to be able to access generated views
Unit 6 Lesson 3: Auth Options and User Managemenet for Integration of BOBJ BI and HANA