Hierarchy
⤷ BC-MID-ICF (Application Component) Internet Communication Framework
⤷ SHTTP (Package) Development Class for HTTP Communication
Basic Data
Data Element | NO_SESSION_MANAGEMENT |
Short Description | Usage/Generation of Security Sessions |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NO_SESSION_MANAGEMENT | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
As a rule, it is desirable that after successful logon a security session and/or a logon ticket is generated. However, this is not appropriate or desirable in all cases.
For some applications (for example, SOAP-based Web services), both the generation and the use of security sessions and logon tickets is not desired. Logon tickets should be accepted, but not generated.
Other applications (for example, OData services, ABAP push channels) want to use existing security sessions and logon tickets, but want to prevent the generation of security sessions and logon tickets.
Use
Switch Value Security Sessions Logon Tickets
Unlimited Use and Generation Possible Use and generation possible
Partly restricted Only use possible Only use possible
Completely restricted Neither use nor generation possible Only use possible
Dependencies
The general activation/deactivation of security sessions (for each ABAP client) is possible using the transaction SICF_SESSIONS. Using the ICF service configuration, only the use of activated security can be restricted; it is possible to activate Security Session Management.
The profile parameter login/create_sso2_ticket defines whether logon tickets can be generated. If the generation of logon tickets is deactivated using the profile parameter, it cannot be activated using the ICF service configuration.
Example
History
Last changed by/on | SAP | 20141013 |
SAP Release Created in | 740 |