URL Maintenance

Field or Control	Description
Description	Users can search for URLs by description.
URLID	Enter the entire URL. Note:For the file attachment functionality, in specifying the URL for the FTP server, the FTP server's machine name can be more than 30 characters, but the length of the full URL is limited to 120 characters. The URL format for file attachments stored in the database is record://recordname, as in record://ABSENCE_HIST_DB.
Comments	This field can be used to make notations and comments and is not displayed elsewhere.
URL Properties	Assign properties to various URL types. See Specifying URL Properties.

Adding New URLs

To add a new URL entry:

Select PeopleTools, and then Utilities, and then Administration, and then Maintain URLs.
Click Add a New Value.

Enter the name that you want to use to identify the new URL address.
Select Add.
Enter the Description, URL, and Comment, if any.
Select URL Properties and specify the required properties.

See the following sections for details.
Select Save.

You must save the page before you can add another URL, or update or display existing URL addresses.
Select Add to add another URL.

Viewing and Updating Existing URLs

To update or display existing URLs:

From the URL Maintenance search page, click Search.
Select the URL Identifier link that you want to update from the Search Results.
Make changes to the page and save.

Specifying URL Properties

You access the URL Properties page by clicking the URL Properties link on the URL Maintenance page.

This example illustrates the fields and controls on the URL Properties page. You can find definitions for the fields and controls later on this page.

You create the URLID using the URL Maintenance page, but you assign various properties to the URLID using the URL Properties page. The properties you assign depend on the protocol and the type of security you are implementing.

The Password Encryption box enables you to encrypt a password value that you intend to assign to the PASSWORD property. Click Encrypt to encrypt the password, then copy the encrypted password into the edit box for the PASSWORD property. The value of this property must be the user password in an encrypted form.

Select the Manage Properties link if you need to add any LibCurl properties that are not PeopleSoft-delivered.

See Maintain URL Properties.

Note:

If you intend to implement secure FTP, SFTP, HTTP, or HTTPS, Oracle recommends you understand the details and behavior of the attachment PeopleCode constructs, such as AddAttachment.

See PeopleCode Developer’s Guide: Understanding the File Attachment Functions.

Specifying FTP/FTPS URLs

FTP over SSL (FTPS) can be achieved in two ways: implicit and explicit. Implicit SSL uses ftps:// and explicit uses ftp://.

To use passive mode (PASV) only, set URL property EXTENDEDPASSIVEMODE to 0.

To assign properties to FTP and FTPS URLs:

On the URL Maintenance page, add a URL value containing ftp:// or ftps:// in the URLID field.
Click Save.
Click the URL Properties link.
Set the URL properties for the protocol and your security preference.
Select the Manage Properties link if you need to add any LibCurl properties that are not PeopleSoft-delivered.
Click Save.

The URL properties for the FTP and FTPS protocols are listed in the following table:

Properties	Description
ACTIVEMODE	To enable active mode, add the ACTIVEMODE property to the URL and set it to Y. The default FTP connection mode is extended passive mode.
ACTIVEPORTOPTION	This property can be used along with ACTIVEMODE. When active mode is enabled, you can use ACTIVEPORTOPTION to specify the IP address and port on which the FTP server can be accessed. This is useful when the server is behind a firewall. By default, ACTIVEPORTOPTION uses the default IP address of your system. If you want to use a particular IP address, set the ACTIVEPORTOPTION value to either the full IP address, a host name to resolve to an IP address, or a local network interface name. You can also specify a port range. For example: 198.51.100.111:10000-13000
CERTALIAS	(Certificate Alias) The Certificate Alias must be an alias name of a certificate stored in the database (using the PeopleTools Digital Certificates page). Note:Currently, only PEM certificates are supported for FTPS.
ENABLEEPRT	This option can be used only with Active Mode. If Active Mode is enabled and ENABLEEPRT is set to N, then the system will use a PORT (IPv4) Active Mode connection. By default, ENABLEEPRT is Y, if Active Mode is set to Y.
EXTENDEDPASSIVEMODE	Enables you to control whether extended passive mode (EPSV) will be used by FTP. To enable select 1, to disable select 0. EPSV is used by default. That is, by default, this value is considered to be 1. If the client fails to connect to the server with EPSV, then the system will try passive mode (PASV). To use PASV only, add EXTENDEDPASSIVEMODE to the URL Properties and set it to 0.
FILE_EXT_LIST	Select the name of a file extension list created using the File Extension List page. A file extension list enables you to restrict file attachment features to work only with appropriate file types, and reject those file types that you believe may be suspicious, potentially harmful, or not appropriate for a particular call to a file-processing built-in PeopleCode function. See File Extension List.
JKSPASSWORD	Enter the password to access and maintain certificates in the JKS keystore/truststore.
JKSPATH	Enter the path where the JKS keystore/truststore file is maintained.
KEYSTOREPASSWORD	Required for FTPS and HTTPS repositories. For attachments transferred from the PeopleSoft system to the FTPS or HTTPS repository, the system retrieves the key pair for the client certificate from the digital certificate store and writes them to a file in PKCS12 format with password protection. The value of this property will be used as the password for the PKCS12 file. The PKCS12 file enables connection and file transfer, and it exists only temporarily in <PS_SERVDIR>\files\<CERT ALIAS NAME> for the duration of the file transfer. The system deletes the file after the file transfer transaction. Note:If the system fails to delete the certificate alias file, a message will be written to the application sever log. The maximum number of files that can exist at any time is equal to the total number of FTPS and HTTPS URL identifiers defined in the system.
PASSWORD	The password associated with the USER property, which identifies the FTP user ID. The value of this property must be the user password in an encrypted form.
SSLUSAGELEVEL	0 - No SSL: No SSL will be used. 1 - Try SSL: Try using SSL, but proceed as normal otherwise. 2 - Control: Require SSL for the control connection. 3 - SSL Only: (Default) Require SSL for all communication.
USER	The FTP user ID used for authentication when accessing the FTP site.
VERIFYHOST	0: Do not verify the server for host name. 1: (Default) Checks for a match with the host name in the URL with the common name or Subject Alternate field in the server certificate.
VERIFYPEER	False: Do not verify the peer. True: (Default) Verify the peer by authenticating the certificate sent by the server.

Specifying SFTP URLs

With SFTP, these authentication methods are supported:

password.
key authentication.

Note:

With key authentication, you have two choices: storing the public and private keys as files within the file system, or storing the public and private keys within an SSH certificate added using the Digital Certificates page.

To set up password authentication create a URL identifier with an SFTP URL value, such as sftp://198.51.100.122/, then set these URL properties:

AUTHTYPE: 2 - PASSWORD
USER: user ID
PASSWORD: encrypted user password

For public key authentication with key files stored in the file system, you can copy the public key file to <PS_SERVDIR>\sshkeys\public and the private key file to <PS_SERVDIR>\sshkeys\private. Alternatively, you can copy the key files to a different location and define an environment variable PS_SSHKEYPATH.

Note:

PS_SSHKEYPATH can replace only PS_SERVDIR. The following directory structure must exist in your custom location, .\sshkeys\public and .\sshkeys\private. For example, <PS_SSHKEYPATH>\sshkeys\public.

If storing the SSH key data in the file system, set these URL properties appropriately:

AUTHTYPE: (1 - PUBLIC KEY)
USER
PRIVATEKEY
PUBLICKEY
PASSWORDKEY

For public key authentication with an SSH certificate stored in the PeopleTools keystore, save the private key and public key data to the database using the Digital Certificates page (PeopleTools, Security, Security Objects, Digital Certificates page). If your SSH certificate is stored in the database by way of the Digital Certificates page, set these URL properties appropriately:

AUTHTYPE: (1 - PUBLIC KEY)
USER
SSHKEYALIAS
PASSWORDKEY

Note:

Oracle recommends storing the SSH public and private key data in the database by creating an SSH certificate stored in the PeopleTools keystore for increased security and ease of maintenance. If the private key and public key files are stored in the file system, Oracle recommends implementing a password-protected private key.

For more information on the Digital Certificates page, see Security Administration: Configuring Digital Certificates

To assign properties to SFTP URLs:

On the URL Maintenance page, add a URL value containing sftp:// in the URLID field.
Click Save.
Click the URL Properties link.
Set the URL properties for the protocol and your security preference.
Select the Manage Properties link if you need to add any LibCurl properties that are not PeopleSoft-delivered.
Click Save.

The URL properties for the SFTP protocol are listed in the following table:

Properties	Description
AUTHTYPE	Select the authentication type: Public Key Password Any
FILE_EXT_LIST	Select the name of a file extension list created using the File Extension List page. A file extension list enables you to restrict file attachment features to work only with appropriate file types, and reject those file types that you believe may be suspicious, potentially harmful, or not appropriate for a particular call to a file-processing built-in PeopleCode function. See File Extension List.
PASSWORD	The password associated with the USER property, which identifies the FTP user ID. The value of this property must be the user password in an encrypted form.
PASSWORDKEY	Enter the password for the private key.
PRIVATEKEY	Select the private key.
PUBLICKEY	Select the public key.
SSHKEYALIAS	Select the SSH certificate saved to the database using the PeopleTools Security, Digital Certificates page (PeopleTools, Security, Security Objects, Digital Certificates). The SSH certificate added through the Digital Certificates page contains both the public and private key data, identified by the Alias column value on the Digital Certificates page. If using the SSHKEYALIAS URL property, the Property Value prompt displays only the list of SSH certificates that have been added to the Digital Certificates page. If you have added the SSH certificate using the Digital Certificates page, and you have assigned an SSH certificate to the SSHKEYALIAS URL property, the system ignores the PUBLICKEY and PRIVATEKEY properties, regardless if they refer to valid key files in the file system. If you provided a password (or passphrase) when generating your SSH certificate, specify that value using the PASSWORDKEY URL property. See Security Administration: Configuring Digital Certificates
USER	Specify the user ID to be authenticated.

Specifying Properties for HTTP URLs

To assign properties to HTTP URLs:

On the URL Maintenance page, add a URL value containing http:// in the URLID field.
Click Save.
Click the URL Properties link.
Set the URL properties for the protocol and your security preference.
Select the Manage Properties link if you need to add any LibCurl properties that are not PeopleSoft-delivered.
Click Save.

The available URL properties for the HTTP protocol are listed in the following table:

Properties	Description
CLOUDPROVIDER	If CLOUDREPOSITORY is set to Y, select one of the available cloud service providers.
CLOUDREPOSITORY	Enter Y if the URL is a cloud repository, and N if it is not.
FILE_EXT_LIST	Select the name of a file extension list created using the File Extension List page. A file extension list enables you to restrict file attachment features to work only with appropriate file types, and reject those file types that you believe may be suspicious, potentially harmful, or not appropriate for a particular call to a file-processing built-in PeopleCode function. See File Extension List.
FOLDERPATH	If CLOUDREPOSITORY is set to Y, enter the location in cloud storage where you want the report to be stored. The folder will be created if it does not exist.
GENERATEACCESSKEY	If CLOUDREPOSITORY is set to Y: Set to Y if you want the ShareAttachment API to generate an access key and set it back, if an access key is not passed in to the API. Set to N if you don't want the ShareAttachment API to generate an access key, when an access key is not passed in to the API.
PASSWORD	The password associated with the USER property, which identifies the user ID. The value of this property must be the user password in an encrypted form. If CLOUDREPOSITORY is set to Y, enter the encrypted password for the cloud account where the reports will be stored.
PROXY	Specify the proxy server (if used).
PROXYPORT	Specify the proxy server port (if used)
USEAUTHTOKEN	Uses the PS_TOKEN authentication cookie, if single sign-on is configured between source and target destination. Note:This must be set to Y if a PeopleSoft web server is used for the HTTP repository.
USER	Specify the user ID to be authenticated. Note:USER must be set if a PeopleSoft web server is used for the HTTP repository. If CLOUDREPOSITORY is set to Y, enter the user name for the cloud account where the reports will be stored.

Specifying Properties for HTTPS URLs

To assign properties to HTTPS URLs:

On the URL Maintenance page, add a URL value containing https:// in the URLID field.
Click Save.
Click the URL Properties link.
Set the URL properties for the protocol and your security preference.
Select the Manage Properties link if you need to add any LibCurl properties that are not PeopleSoft-delivered.
Click Save.

The available URL properties for the HTTPS protocol are listed in the following table:

Properties	Description
ACCESSTOKEN	Enter a password that you encrypted using the Password Encryption utility on the URL Properties page.
ACCOUNTID	Enter your Twilio account ID Use this property for push notifications. See Fluid User Interface Developer’s Guide: Managing Global Settings
BUCKETNAME	If you are using Oracle Cloud Infrastructure as a file repository, enter the name of the bucket you created in the Object Storage service. See Specifying URLs for Oracle Cloud Infrastructure.
CERTALIAS	(Certificate Alias) The Certificate Alias must be an alias name of a certificate stored in the database (using the PeopleTools Digital Certificates page). Note:Currently, only PEM certificates are supported for FTPS.
CLIENTID	Use when defining URL properties for SharePoint. See Defining SharePoint Repositories
CLIENTSECRET	Use when defining URL properties for SharePoint. See Defining SharePoint Repositories
CLOUDPROVIDER	If CLOUDREPOSITORY is set to Y, select one of the available cloud service providers.
CLOUDREPOSITORY	Enter Y if the URL is a cloud repository, and N if it is not.
DOCUMENTLIBRARY	Use when defining URL properties for SharePoint. See Defining SharePoint Repositories
FILE_EXT_LIST	Select the name of a file extension list created using the File Extension List page. A file extension list enables you to restrict file attachment features to work only with appropriate file types, and reject those file types that you believe may be suspicious, potentially harmful, or not appropriate for a particular call to a file-processing built-in PeopleCode function. See File Extension List.
FINGERPRINT	If you are using Oracle Cloud Infrastructure as a file repository, enter the fingerprint for the API signing key. See Specifying URLs for Oracle Cloud Infrastructure.
FOLDERPATH	If CLOUDREPOSITORY is set to Y, enter the location in cloud storage where you want the report to be stored. The folder will be created if it does not exist.
GENERATEACCESSKEY	If CLOUDREPOSITORY is set to Y: Set to Y if you want the ShareAttachment API to generate an access key and set it back if an access key is not passed in to the API. Set to N if you don't want the ShareAttachment API to generate an access key, when an access key is not passed in to the API.
KEYSTOREPASSWORD	Required for FTPS and HTTPS repositories. For attachments transferred from the PeopleSoft system to the FTPS or HTTPS repository, the system retrieves the key pair for the client certificate from the digital certificate store and writes them to a file in PKCS12 format with password protection. The value of this property will be used as the password for the PKCS12 file. The PKCS12 file enables connection and file transfer, and it exists only temporarily in <PS_SERVDIR>\files\<CERT ALIAS NAME> for the duration of the file transfer. The system deletes the file after the file transfer transaction. Note: If the system fails to delete the certificate alias file, a message will be written to the application sever log. The maximum number of files that can exist at any time is equal to the total number of FTPS and HTTPS URL identifiers defined in the system.
KEYPASSPHRASE	If you are using Oracle Cloud Infrastructure as a file repository, enter the encrypted passphrase for the API signing key pair. See Specifying URLs for Oracle Cloud Infrastructure.
NAMESPACENAME	If you are using Oracle Cloud Infrastructure as a file repository, enter the namespace that you created in Object Storage service. See Specifying URLs for Oracle Cloud Infrastructure.
PASSWORD	The password associated with the USER property, which identifies the user ID. The value of this property must be the user password in an encrypted form. If CLOUDREPOSITORY is set to Y, enter the encrypted password for the cloud account where the reports will be stored.
PRIVATEKEYPATH	If you are using Oracle Cloud Infrastructure as a file repository, enter the full path to the location where you saved the API signing key pair. See Specifying URLs for Oracle Cloud Infrastructure.
PROXY	Specify the proxy server (if used).
PROXYPORT	Specify the proxy server port (if used).
SHAREPOINTREPOSITORY	Use when defining URL properties for SharePoint. See Defining SharePoint Repositories
SHAREPOINTSITE	Use when defining URL properties for SharePoint. See Defining SharePoint Repositories
SSLUSAGELEVEL	0 - No SSL: No SSL will be used. 1 - Try SSL: Try using SSL, but proceed as normal otherwise. 2 - Control: Require SSL for the control connection. 3 - SSL Only: (Default) Require SSL for all communication.
TENANCYOCID	If you are using Oracle Cloud Infrastructure as a file repository, enter the OCID for your tenancy.
TENANTID	Use when defining URL properties for SharePoint. See Defining SharePoint Repositories
TEXTFROM	Enter the phone number associated with your Twilio account. Use this property for push notifications. See Fluid User Interface Developer’s Guide: Managing Global Settings
USEAUTHTOKEN	Uses the PS_TOKEN authentication cookie, if single sign-on is configured between source and target destination. Note:This must be set to Y if a PeopleSoft web server is used for the HTTP repository.
USER	Specify the user ID to be authenticated. Note:USER must be set if a PeopleSoft web server is used for the HTTP repository. If CLOUDREPOSITORY is set to Y, enter the user name for the cloud account where the reports will be stored.
USEROCID	If you are using Oracle Cloud Infrastructure, enter the user OCID for your account.
VERIFYHOST	0: Do not verify the server for host name. 1: (Default) Checks for a match with the host name in the URL with the common name or Subject Alternate field in the server certificate.
VERIFYPEER	False: Do not verify the peer. True: (Default) Verify the peer by authenticating the certificate sent by the server.

Specifying Properties for URLs for Database Records

To assign properties to URLs for files in the database:

On the URL Maintenance page, add a URL value containing record:// in the URLID field.
Click Save.
Click the URL Properties link.
Set the URL properties for the protocol and your security preference.
Click Save.

The available URL properties for the record protocol are listed in the following table:

Property	Description
FILE_EXT_LIST	Select the name of a file extension list created using the File Extension List page. A file extension list enables you to restrict file attachment features to work only with appropriate file types, and reject those file types that you believe may be suspicious, potentially harmful, or not appropriate for a particular call to a file-processing built-in PeopleCode function. See File Extension List.
IMG_DATA_COLUMN	Enter information about the database record. For information on this property, see PeopleCode Language Reference: ResizeImage function.
IMG_FILE_FORMAT	Enter information about the database record. For information on this property, see PeopleCode Language Reference: ResizeImage function.
IMG_NAME_COLUMN	Enter information about the database record. For information on this property, see PeopleCode Language Reference: ResizeImage function.

Using HTTP/HTTPS File Transfers

HTTP/HTTPS file transfer requires that the http/https repository is available (file storage location). The repository can either be on a PeopleSoft web server or non-PeopleSoft server. The PeopleSoft Internet Architecture provides a handler servlet (psfiletranfer) to handle the requests. If you use a non-PeopleSoft web server you need to create a handler for non-PeopleSoft servers/repositories.

Once the repository is created, the configuration.properties file for the appropriate PeopleSoft site needs to be modified to include the HttpRepository property. For example:

HttpRepositoryPath=D:/HttpRepository

Note:

Use a forward slash (/).

To set up HTTP:

Create a URL identifier using http:// (as in, http://<PIA URL>/psfiletransfer/<sitename>/).
Select these URL properties:
- USEAUTHTOKEN: Y
- USER: user_ID
Set the Authentication Option field on the default local node to Password.

To set up HTTPS:

Set up the target web server for HTTPS.
Add the Root CA and Client Certificate to Digital Certificate store.
Create an URL identifier using https://.
Select these URL properties:
- CERTALIAS: your certificate alias
- SSLUSAGELEVEL: 3-SSL Only
- VERIFYHOST: 1
- VERIFYPEER: Y
- USER: user ID
- USEAUTHTOKEN: Y

You can have the HTTP repository on a separate PeopleSoft web server too. For example, PIAsystem1 can have the URL identifier pointing to a URL on PIAsystem2. This requires the following to be in place:

The user specified in the URL properties must exist in both the systems with the proper permissions.
The default local nodes on both systems should have Authentication Option set to Password and should be pinged successfully.
The default local nodes of each system are added to the single-sign-on list for each database.

Note:

To upload non-ASCII file names to an HTTP Repository, the application server needs to be booted in the native language (such as Japanese or Chinese). If the application server is booted in English, file names with non-ASCII characters will not be uploaded to the HTTP Repository.

See Global Technology: Understanding Character Set Selection for more information on how character sets on various tiers of the PeopleSoft system can affect file attachment processing.

Specifying URLs When Attaching Files

When attaching files, whether you can pass a string URL or only use the URL identifier depends on the protocol and repository type being used. When attaching files, keep these guidelines in mind:

Using the URL Identifier is mandatory for FTPS, SFTP, HTTP, and HTTPS.
Using a URL Identifier is also recommended for FTP.
For Record and File attachment protocols, you can use the URL Identifier or use a URL string (and not reference the stored URL Identifier).

For example, with plain FTP you could use a URL string, such as:

ftp://user:password@site/

Or, if a URL Identifier has been created, which is ftpurl in these examples, you can reference that in one of these formats:

ftp://userid:password@ftpurl/: where the FTP user and FTP password are provided in clear text, but the URL information comes from the URL Identifier.
ftp://userid@ftpurl/: where the FTP user is provided in clear text, but the FTP password and the URL information comes from the URL Identifier.

For this format, provide the rest of the properties (password) by accessing the URL Properties link on the URL Maintenance page.
ftp://ftpurl/: where all the required information comes from the URL Identifier.

For this format, provide the rest of the properties (including user and password) by accessing the URL Properties link on the URL Maintenance page.

Note:

Follow the requirements for the URLID at the beginning of this section.

Specifying URLs for Oracle Content and Experience Cloud Repository

You can use Oracle Content and Experience Cloud as a file repository for File Attachments and Process Scheduler Report Distribution. To define a URL ID for Oracle Content and Experience Cloud as a file repository:

Create a new HTTP or HTTPS URL ID, with the following format.

In this example, <hostname> is the server where the Oracle Content and Experience Cloud storage instance is running, and [port] is the Oracle Content and Experience Cloud port (the port designation is optional).

http://<hostname>:[port]/documents

or

https://<hostname>:[port]/documents
Select URL Properties, and enter values for these properties, using the definitions in the HTTP or HTTPS table earlier in this topic. For example:
- CLOUDREPOSITORY: Y
- CLOUDPROVIDER: Oracle Document Cloud
- FOLDERPATH: /psftfolder/reports
- USER: user ID
- PASSWORD: encrypted password value
- GENERATEACCESSKEY (optional): N
Add the following properties for SSL if necessary, using the definitions in the HTTP or HTTPS table earlier in this topic. For example:
- CERTALIAS: your certificate alias
- SSLUSAGELEVEL: 3 - SSL Only
- VERIFYHOST: 1
- VERIFYPEER: Y

Use this URL with the file attachment APIs to enable the PeopleSoft system to upload attachments from the Oracle Content and Experience Cloud repository. You can also share the uploaded files with other users.

See PeopleCode Language Reference: AddAttachment function

See PeopleCode Language Reference: ShareAttachment function

Use this URL when you define a report node that allows reports to be uploaded to Oracle Content and Experience Cloud.

See Process Scheduler: Defining Report Nodes

For additional information on working with Oracle Content and Experience Cloud repositories, see Using Cloud Repositories.

Specifying URLs for Oracle Cloud Infrastructure Object Storage

You can use Oracle Cloud Infrastructure Object Storage as a file repository for File Attachments and Process Scheduler Report Distribution. This process requires that you have an account for Oracle Cloud Infrastructure Object Storage service. You enter account details in specifying the URL.

For information on getting an Oracle Cloud Infrastructure account, see Welcome to Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

To define a URL ID for Oracle Cloud Infrastructure Object Storage as a file repository.

Get the tenancy OCID and user OCID for your Oracle Cloud Infrastructure account.

See Required Keys and OCIDs in the Oracle Cloud Infrastructure online documentation.
Generate an API signing key pair and get the fingerprint of the public API signing key for your Oracle Cloud Infrastructure account.

See Required Keys and OCIDs in the Oracle Cloud Infrastructure online documentation.

If you used a passphrase in creating the API signing key pair, as recommended, get the passphrase.
Create a bucket and namespace for the files in Oracle Cloud Infrastructure Object Storage.

See Overview of Object Storage in the Oracle Cloud Infrastructure documentation.
In your PeopleSoft environment, install an application server-based digital certificate.

See Security Administration: Installing Application Server-Based Digital Certificates
In your PeopleSoft environment, create a new URL using https://.
Enter the Object Service Storage API endpoint in the URLID field on the URL Maintenance page.

The Object Service Storage API endpoints are available in the Oracle Cloud Infrastructure online documentation.

See API Reference and Endpoints.
Select URL Properties, and enter values for these properties:
- CLOUDREPOSITORY: Y
- CLOUDPROVIDER: OCI Object Storage
- BUCKETNAME: The name of the bucket you created in Object Storage.
- TENANCYOCID: The OCID for your Oracle Cloud Infrastructure tenancy.
- USEROCID: The OCID of the user calling the API.
- FINGERPRINT: The fingerprint for the API key pair being used.
- PRIVATEKEYPATH: The full path to the location where you saved the API signing key pair.
- KEYPASSPHRASE: The encrypted passphrase for the API signing key pair.
  
  Use the Password Encryption fields to encrypt the passphrase. See Specifying URL Properties in this section.
Add the following properties for SSL if necessary, using the definitions in the HTTP or HTTPS table earlier in this topic. For example:
- SSLUSAGELEVEL: 3 - SSL Only
- VERIFYHOST: 1
- VERIFYPEER: Y

Use this URL with the file attachment APIs to enable the PeopleSoft system to upload attachments from the Object Storage repository.

See PeopleCode Language Reference: AddAttachment function

Use this URL when you define a report node that allows reports to be uploaded to Object Storage.

See Process Scheduler: Defining Report Nodes