Risk Analysis for Legacy Connector

7/31/2019 Risk Analysis for Legacy Connector

1/24


2/24

2

Table of Contents............................................................................................................................................. 3

................................................................................................................................................ 3

1.1-Legacy File Formats: ....................................................................................................................... 4...................................................................................................... 13

................................................................................................... 15

1.4- Establish relationship between Target connector to Connector Type: ....................................... 18

.................................................................................................... 20

1.5-Running Synch Job for Legacy Connector ..................................................................................... 23

1.6-Execute Risk Analysis for Legacy Connector ................................................................................. 24


3/24

3


4/24


5/24

5

File ID: LEGACY_DEFAULT_USER

User Master File


6/24

6

User Action File

Field DataField

Type

FieldSize

FieldValues

Sorting Req'd Description Transformation

User ID String 50 CAPS Sort Ascending

Order1

Yes User ID Unique record= The

combination of columns 1 3

(User ID,Roles, and

Action From)must be unique

Role Name String 100 CAPS Sort

AscendingOrder2

Yes Role Name

ActionFrom

String 50 CAPS Sort Ascending

Order3

Yes User Action

Action To String 50 CAPS No User Action, onlyapplicable if User Action has range

From/To

If this valuedoes not exist

for sourcesystem, leave

blank

PROFILE String 20 CAPS No If this valuedoes not exist


blank

CompositeRole Name

String 100 CAPS No Composite RoleName (leave blank if

unavailable)



blank.


7/24

7

User Permission File

Field DataFieldType

FieldSize

FieldValues


User ID String 50 CAPS Sort Ascending

Order1

Yes User ID Unique record=Thecombination of columns 1 3(User ID, Roles,and ActionFrom) must beunique

Role Name String 100 CAPS Sort Ascending

Order2

Yes Role Name

Permission(Resource

Name||ResourceExt.)


Order3

User Permission(Permission

Object/Field),required if applicable

ACTION andPERMISSIONfield that use | |with no space in

between.

Auth Group String 20 Auth Group

Value From String 50 CAPS Sort Ascending

Order4

Yes PermissionValue

Value To String 50 CAPS No Permissionvalue, onlyapplicable if User Actionhas rangeFrom/To

If this valuedoes not existfor sourcesystem, leaveblank

Extra Field () String Leave Blank

Profile String 20 CAPS No Profile Name If this valuedoes not existfor source

system, leaveblank

Composite RoleName

String 100 CAPS No Composite RoleName (leaveblank if unavailable)

If this valuedoes not existfor sourcesystem, leaveblank.


8/24

8


9/24

9

Role Permission File

Field DataFieldType

FieldSize

FieldValues


Role String 100 CAPS Sort Ascending

Order1

Yes Role Name

PERMISSION(Resource

Name||Resource

Ext.)


Order2

Yes Role Permission(Permission

Object/Field),required

if applicable

ACTION andPERMISSIONfield that use | |

with no spacein between

Auth Group String 20 Yes Auth Group

Value From String 50 CAPS Yes PermissionValue

Value To String 50 CAPS No Permissionvalue, only

applicable if User Actionhas rangeFrom/To



blank


10/24

10

Profile Master File

Field DataFieldType

FieldSize

FieldValues


Profile String 20 CAPS Sort Ascending

Yes Profile Name Unique recordsonly

ProfileDescription

String 255 Yes Profile Description

Language String 2 CAPS Yes Language

DeletionFlag

String 1 No Deletion Flag(X=True, SPACE =

False)

File ID: LEGACY_PROFILE_ACTION

Profile Action File

Field DataFieldType

FieldSize

FieldValues


Profile String 20 CAPS Sort

AscendingOrder1

Yes Profile Name

ActionFrom


Order2

Yes Profile Action

Action To String 50 CAPS No Profile Action, onlyapplicable if User Action has range

From/To



blank


11/24

11

File ID: LEGACY_PROFILE_PERMISSION

Profile Permission File

Field DataFieldType

FieldSize

FieldValues


Profile String 20 CAPS Sort

AscendingOrder1

Yes Profile Name

PERMISSION(Resource

Name||ResourceExt.)


Order2

Yes Profile Permission(Permission

Object/Field),required if applicable

ACTION andPERMISSIONfield that use | |with no space

in between

Auth Group String 2 Yes Auth Group

Value From String 50 CAPS Yes Permission

Value

Value To String 50 CAPS No Permissionvalue, only

applicable if User Actionhas rangeFrom/To



blank

File ID: LEGACY_ACTIONS

Field

TCODEString 32 CAPS Sort

AscendingOrder1

Yes Transaction Code

TCODEDescription

String 255 Transaction CodeDescription

LANGUAGE String 2 CAPS Yes Language


12/24

12

File ID: LEGACY_PERMISSION

Permission File

Field DataFieldType

FieldSize

FieldValues


ResourceName


Order1

Yes Resource Name

ResourceText

String 50 Resource Text

LANGUAGE String 2 CAPS Yes Language


13/24

13


14/24

14


15/24

15

assign Physical

path to each Logical file path


16/24

16


17/24

17


18/24

18

1.4- Establish relationship between Target connector to Connector Type:


19/24


20/24

20


21/24

21
http://vmw3053.wdf.sap.corp:50000/irj/portal


22/24

22


23/24

23

1.5-Running Synch Job for Legacy Connector For Authorization Synch:

1. Transaction SPRO- SAP Reference IMG Governance, Risk Compliance Access Control Synchronization Jobs Authorization Synch Execute

For User and Role Synch

Transaction SPRO- SAP Reference IMG Governance, Risk Compliance Access Control Synchronization Jobs Repository Object Synch Execute


24/24

Documents

Risk Analysis for Legacy Connector