BV.Identity Validation.SAP
|
BV | Identity Validation SAP | Version: | 0.21 | 
|
|---|---|---|---|---|---|
| Document type: | Building Block Variant | Owner: |
Variant Coordinates
This Building Block Variant...
| ... belongs to Working Area: | Middleware (MW) |
| ... is an implementation of Building Block Type: | Identity Validation |
| ... is intended for use in Environment: |
Description
SAP Authentication (native).
Business purpose
The purpose is to authenticate a user that requests access to a SAP application against the proprietary SAP Authentication Application either in a local solution (UA) of a central (shared) solution (CUA).
If Single Sign On is required, CUA (and TAM) are required. The user base is also a determiner between UA and CUA. If the user base is internal (ArchiSurance own or hired personnel) either the UA or CUA option can be used. If the user base is external of a mix of internal and external UA is used. Single Sign is then only possible if an exception is granted for the external users.
Characteristics & indications of usage
The authentication data are maintained and deployed from the Central User Administration (CUA). This will provide the organization with a single point of administration and an excellent overview which user is authorized on which systems and for which activities. The Authentication and Authorization facilities are integrated in one application. Note: in the text below, we still need to add elements
- Oracle
- High Availability software
Elements
When designing a facility to implement this function, inclusion of all the following elements is prescribed; either mandatory, optional or explicitly forbidden:
| Element | Type | Prescribed | Rationale |
| Central User Administration (CUA) | mandatory | Software component | |
| EL.User Administration (UA) |  Click to create!
|
mandatory | Software component |
| Red Hat Enterprise Linux (SmartHat) | mandatory | Cost and the SAP Product Availability Matrix |
Quality Requirements
When a facility is designed according to this architectural recipe, it must/will satisfy the following Quality Requirements. This is the responsibility of the infrastructure designer. Note that because of the specified Elements (either the mandatory Elements and any applied optional Elements), some of these Requirements might automatically be satisfied.
| QA Group | Quality Attribute | Value |
|---|---|---|
| Flexibility | Adaptability | HSC |
| Scalability | up | |
| Maintainability | Manageability | Medium |
| Accountability | SP | |
| Reliability | Availability | High |
| Integrity | Low |
Used by pattern(s)
Below is shown which Pattern Variant(s) (if any) currently use this Building Block Variant:
No Pattern Variant based on this Building Block Variant (yet)
Facility Implementation Blueprint(s)
Below is shown which Building Block Blueprint(s) (if any) have been created for this Building Block Variant:
No Solution Blueprint based on this Variant (yet)