0% found this document useful (0 votes)
34 views2 pages

The Reginfo File Is Holding Rules Controlling Which Remote Servers

reginfo

Uploaded by

Manisha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
34 views2 pages

The Reginfo File Is Holding Rules Controlling Which Remote Servers

reginfo

Uploaded by

Manisha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

The reginfo file is holding rules controlling which remote servers (based

on their hostname/ip-address) are allowed to either register, access


or cancel which 'Registered Server Programs' (based on their program
alias (also known as 'TP name')).

'gw/reg_info – location

contains rules related to 'Registered external RFC Servers'.

P/D Host=which servers are allowed to register ACCESS=.which RFC


clients are allowed to talk to the 'Registered Server Program' CANCEL

Internal rule : by sap

This rule is generated when gw/acl_mode = 1 is set but no custom reginfo


was defined.

Last rule in custom reginfo file.

P TP=* HOST=internal,local ACCESS=internal,local


CANCEL=internal,local

The secinfo file is holding rules controlling which programs (based on


their executable name or fullpath, if not in $PATH) can be started by
which user calling from which host(s) (based on its hostname/ip-
address) on which RFC Gateway server(s) (based on their
hostname/ip-address).

'gw/sec_info

SAP introduced an internal rule in the secinfo ACL to allow the starting of
any programs on the same server :

P USER=* USER-HOST=internal,local HOST=internal,local TP=*

The prxyinfo file is holding rules controlling which source systems (based
on their hostname/ip-address) are allowed to talk to which destination
systems (based on their hostname/ip-address) over the current RFC
Gateway.

gw/prxy_info
The location of the prxyinfo ACL file is specified by the profile
parameter gw/prxy_info.

1. if it specifies a permit or a deny. This is defined by the letter P or Dat


the beginning of a rule.

2. which source is allowed to proxy. This is defined in SOURCE=.

3. which target is allowed to be reached. This is defined in DEST=.

P SOURCE=internal DEST=*

P SOURCE=local DEST=*

P SOURCE=internal,local DEST=local

You might also like