Upload Attachments to OCI Object Store

We’ve added improvements to the LPN Inquiry transaction process, specifically focused on attachment handling. This update changes the location where attachments will be stored. Once the setup steps are done, attachments will be stored in the customer’s own cloud object store. This update marks a significant step towards providing our users with more control and flexibility in managing their attachments. Users will be able to control the retention policy, backups etc. according to their own policies.

INTRODUCING THE 'OCI-OBJECT STORE' SAAS CONFIGURATION TYPE

We’ve created a new SaaS Configuration type, "OCI Object Store," to facilitate API key-based authentication for secure attachment uploads. This configuration includes the following parameters:

  • App parm3 (user_ocid): Stores the user's OCID (Oracle Cloud Identifier).
  • App parm4 (Fingerprint): Holds the fingerprint associated with the user's API key.
  • App parm5 (tenancy_ocid): Contains the tenancy OCID for the user's Oracle Cloud account.
  • App parm6 (Region): Specifies the Oracle Cloud region where the Object Storage resides.
  • App parm7 (Bucket Name): Specifies the OCI Object Store bucket designated to store the uploaded objects.
  • App parm8 (Private Key): Specifies a valid RSA private key.

TRANSITIONING TO CUSTOMER OBJECT STORE

We understand the importance of a smooth transition, so for a limited time, we will continue to use our own object storage to ensure uninterrupted service. During this period, we will work on migrating existing attachments to the customer's Object Store, ensuring a seamless transition to the new storage system.

ATTACHMENT MIGRATION MADE EASY

The new Migrate Attachments button simplifies the process of migrating attachments to your customer-hosted object store buckets. This migration process runs in the background, ensuring it doesn't disrupt your workflow. Once initiated, you'll receive a notification about the migration status, and the system will guide you to check the progress. Note that if you try to upload an attachment, but do not have Object Store configured, an error will display, and you will need to follow the steps to setup a new SaaS App Configuration with the app name OCI-Object Store,.

NOTE: The migration can be performed only once to ensure a seamless transition to your configured bucket.

  • The Migrate Attachments button will only be enabled for customers that are currently using the WMS bucket.
  • If the Migrate Attachments is enabled and you want to migrate to your new bucket, a confirmation message displays that the migration is in progress.
  • If there is nothing to migrate, a message "No attachments to migrate" displays.
  • If no SaaS App Configuration is set up, the message "SaaS App Config not found! Cannot migrate attachments" displays.

CONNECTIVITY TEST FOR APP CONFIGURATION

When you set up a new SaaS App Configuration with the app name OCI-ObjectStore, our system will automatically perform a connectivity test to ensure a successful connection to your configured bucket.
This ensures that your configuration is valid before saving, providing immediate feedback on any potential issues. If the test succeeds, the record is created, but if it fails, the save process is blocked, and an error message prompts you to check your credentials.

CHANGE HISTORY FOR ENHANCED SECURITY

You can now click the new Change History button, and a detailed screen will display a searchable history with fields such as App Name, Modification User, Action (update/create/delete), Modification Timestamp, and more. This allows you to track modifications to your app configurations, providing an audit trail for enhanced security. This functionality mirrors the existing Endpoints screen history, giving you a comprehensive overview of changes.

Steps to Enable

To configure a new SaaS App Configuration with the app name OCI-ObjectStore:

  1. From the SaaS App Configuration UI, create a new Saas App Configuration.
  2. From the App Name drop-down, select OCI-OBJECTSTORE.
  3. Include the Base URL and add any App Parameter details needed.
  4. Click Save. A record will then be visible in the SaaS App Configuration UI.