Skip to content

/AWS1/IF_TRN=>UPDATEACCESS()

About UpdateAccess

Allows you to update parameters for the access specified in the ServerID and ExternalID parameters.

Method Signature

METHODS /AWS1/IF_TRN~UPDATEACCESS
  IMPORTING
    !IV_HOMEDIRECTORY TYPE /AWS1/TRNHOMEDIRECTORY OPTIONAL
    !IV_HOMEDIRECTORYTYPE TYPE /AWS1/TRNHOMEDIRECTORYTYPE OPTIONAL
    !IT_HOMEDIRECTORYMAPPINGS TYPE /AWS1/CL_TRNHOMEDIRECTORYMAP00=>TT_HOMEDIRECTORYMAPPINGS OPTIONAL
    !IV_POLICY TYPE /AWS1/TRNPOLICY OPTIONAL
    !IO_POSIXPROFILE TYPE REF TO /AWS1/CL_TRNPOSIXPROFILE OPTIONAL
    !IV_ROLE TYPE /AWS1/TRNROLE OPTIONAL
    !IV_SERVERID TYPE /AWS1/TRNSERVERID OPTIONAL
    !IV_EXTERNALID TYPE /AWS1/TRNEXTERNALID OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_trnupdateaccessrsp
  RAISING
    /AWS1/CX_TRNINTERNALSVCERROR
    /AWS1/CX_TRNINVALIDREQUESTEX
    /AWS1/CX_TRNRESOURCEEXISTSEX
    /AWS1/CX_TRNRESOURCENOTFOUNDEX
    /AWS1/CX_TRNSERVICEUNAVAILEX
    /AWS1/CX_TRNTHROTTLINGEX
    /AWS1/CX_TRNCLIENTEXC
    /AWS1/CX_TRNSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

iv_serverid TYPE /AWS1/TRNSERVERID /AWS1/TRNSERVERID

A system-assigned unique identifier for a server instance. This is the specific server that you added your user to.

iv_externalid TYPE /AWS1/TRNEXTERNALID /AWS1/TRNEXTERNALID

A unique identifier that is required to identify specific groups within your directory. The users of the group that you associate have access to your Amazon S3 or Amazon EFS resources over the enabled protocols using Transfer Family. If you know the group name, you can view the SID values by running the following command using Windows PowerShell.

Get-ADGroup -Filter {samAccountName -like "YourGroupName*"} -Properties * | Select SamAccountName,ObjectSid

In that command, replace YourGroupName with the name of your Active Directory group.

The regular expression used to validate this parameter is a string of characters consisting of uppercase and lowercase alphanumeric characters with no spaces. You can also include underscores or any of the following characters: =,.@:/-

Optional arguments:

iv_homedirectory TYPE /AWS1/TRNHOMEDIRECTORY /AWS1/TRNHOMEDIRECTORY

The landing directory (folder) for a user when they log in to the server using the client.

A HomeDirectory example is /bucket_name/home/mydirectory.

You can use the HomeDirectory parameter for HomeDirectoryType when it is set to either PATH or LOGICAL.

iv_homedirectorytype TYPE /AWS1/TRNHOMEDIRECTORYTYPE /AWS1/TRNHOMEDIRECTORYTYPE

The type of landing directory (folder) that you want your users' home directory to be when they log in to the server. If you set it to PATH, the user will see the absolute Amazon S3 bucket or Amazon EFS path as is in their file transfer protocol clients. If you set it to LOGICAL, you need to provide mappings in the HomeDirectoryMappings for how you want to make Amazon S3 or Amazon EFS paths visible to your users.

If HomeDirectoryType is LOGICAL, you must provide mappings, using the HomeDirectoryMappings parameter. If, on the other hand, HomeDirectoryType is PATH, you provide an absolute path using the HomeDirectory parameter. You cannot have both HomeDirectory and HomeDirectoryMappings in your template.

it_homedirectorymappings TYPE /AWS1/CL_TRNHOMEDIRECTORYMAP00=>TT_HOMEDIRECTORYMAPPINGS TT_HOMEDIRECTORYMAPPINGS

Logical directory mappings that specify what Amazon S3 or Amazon EFS paths and keys should be visible to your user and how you want to make them visible. You must specify the Entry and Target pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it is displayed as is. You also must ensure that your Identity and Access Management (IAM) role provides access to paths in Target. This value can be set only when HomeDirectoryType is set to LOGICAL.

The following is an Entry and Target pair example.

[ { "Entry": "/directory1", "Target": "/bucket_name/home/mydirectory" } ]

In most cases, you can use this value instead of the session policy to lock down your user to the designated home directory ("chroot"). To do this, you can set Entry to / and set Target to the HomeDirectory parameter value.

The following is an Entry and Target pair example for chroot.

[ { "Entry": "/", "Target": "/bucket_name/home/mydirectory" } ]

iv_policy TYPE /AWS1/TRNPOLICY /AWS1/TRNPOLICY

A session policy for your user so that you can use the same Identity and Access Management (IAM) role across multiple users. This policy scopes down a user's access to portions of their Amazon S3 bucket. Variables that you can use inside this policy include ${Transfer:UserName}, ${Transfer:HomeDirectory}, and ${Transfer:HomeBucket}.

This policy applies only when the domain of ServerId is Amazon S3. Amazon EFS does not use session policies.

For session policies, Transfer Family stores the policy as a JSON blob, instead of the Amazon Resource Name (ARN) of the policy. You save the policy as a JSON blob and pass it in the Policy argument.

For an example of a session policy, see Example session policy.

For more information, see AssumeRole in the Amazon Web ServicesSecurity Token Service API Reference.

io_posixprofile TYPE REF TO /AWS1/CL_TRNPOSIXPROFILE /AWS1/CL_TRNPOSIXPROFILE

PosixProfile

iv_role TYPE /AWS1/TRNROLE /AWS1/TRNROLE

The Amazon Resource Name (ARN) of the Identity and Access Management (IAM) role that controls your users' access to your Amazon S3 bucket or Amazon EFS file system. The policies attached to this role determine the level of access that you want to provide your users when transferring files into and out of your Amazon S3 bucket or Amazon EFS file system. The IAM role should also contain a trust relationship that allows the server to access your resources when servicing your users' transfer requests.

RETURNING

oo_output TYPE REF TO /aws1/cl_trnupdateaccessrsp /AWS1/CL_TRNUPDATEACCESSRSP

Domain /AWS1/RT_ACCOUNT_ID
Primitive Type NUMC

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->updateaccess(
  io_posixprofile = new /aws1/cl_trnposixprofile(
    it_secondarygids = VALUE /aws1/cl_trnsecondarygids_w=>tt_secondarygids(
      ( new /aws1/cl_trnsecondarygids_w( 123 ) )
    )
    iv_gid = 123
    iv_uid = 123
  )
  it_homedirectorymappings = VALUE /aws1/cl_trnhomedirectorymap00=>tt_homedirectorymappings(
    (
      new /aws1/cl_trnhomedirectorymap00(
        iv_entry = |string|
        iv_target = |string|
        iv_type = |string|
      )
    )
  )
  iv_externalid = |string|
  iv_homedirectory = |string|
  iv_homedirectorytype = |string|
  iv_policy = |string|
  iv_role = |string|
  iv_serverid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_serverid = lo_result->get_serverid( ).
  lv_externalid = lo_result->get_externalid( ).
ENDIF.