Technical Evidence
Response validated August 24, 2026
Partner Sandbox
Read-only validation

Integration Case Study

NUPS connected toOracle Hospitality

GlyphLock built a controlled server-to-server bridge between the Nexus Unified Portal System (NUPS) and the Oracle Hospitality Integration Platform, then progressed the Partner Sandbox path through protected configuration, OCIM authentication, request success and sanitized response validation.

Verified outcome

Response validated

On August 24, OAuth and a read-only room-configuration request succeeded; the sanitized response was validated.

250 scanned · 250 review · 0 writes

Server settings

7 / 7 present

Authentication

OCIM accepted

August 24 maturity

Response validated

Historical August 12 latency

921 ms

Historical baseline: the August 12 Partner Sandbox record shows OCIM OAuth, a read-only OHIP request, HTTP success and 921 ms latency. The 921 ms value is not attributed to the August 24 test.

The 250 scanned records were sanitized Oracle Partner Sandbox room-configuration rows. Every row failed at least one local mapping-preflight rule—such as room-number formatting, a missing room-type code, or inactive status—so all 250 were flagged for human review and no write was attempted.

The challenge

Connect hospitality infrastructure without moving trust into the browser

NUPS needed to prove that it could authenticate with Oracle while keeping application credentials outside client code. A simple “configured” badge was not enough: the integration needed a controlled live test with bounded calls and usable evidence.

The implementation separated presence checks from outbound testing, restricted both operations to the designated integration owner and returned only operational metadata. The browser never received an OAuth token or Oracle response payload.

Architecture

Four controlled boundaries

01

GlyphLock NUPS

Exact integration-owner control inside the Base44 application.

02

Secure Base44 Function

Validates configuration, creates request IDs, enforces HTTPS and keeps credentials server-side.

03

Oracle OAuth

OCIM client-credentials exchange against the OHIP Partner Sandbox.

04

OHIP Property API

Authorized, read-only property and room-configuration requests validated the sandbox response path.

Security controls implemented

Exact integration-owner enforcement before status or test execution

Seven required server settings checked without returning their values

HTTPS-only OHIP gateway validation

Unique request ID for OAuth and Property API traceability

15-second timeout on each outbound request

No access token, guest data, credential value or Oracle payload returned to the browser

Read-only verification call; no reservation, payment or profile record was changed

Scope boundary

This milestone verifies transport and authorization in Oracle’s Partner Sandbox. It does not claim a production hotel rollout, reservation synchronization, payment processing, guest-profile migration or Simphony Register certification.

What changed during the test

No business record changed. The August 24 validation requested server-side OAuth and read sanitized property and room-configuration data from the shared Partner Sandbox.

Execution record

From onboarding to verified connection

01

Oracle environment established

GlyphLock received OHIP onboarding access and prepared its Partner Sandbox application and property configuration.

02

Secrets isolated server-side

Gateway, authentication, application and property values were stored as Base44 server secrets rather than frontend variables.

03

Readiness control built

A protected OHIP readiness page and backend function were added to verify configuration without displaying credentials.

04

Deployment mismatch resolved

The readiness route initially returned 404 because the source existed ahead of the production frontend release. The correct Glyphlock app was published and the route verified live.

05

OCIM configuration normalized

A legacy onboarding value stored the Oracle OAuth scope where the scheme label was expected. The backend normalized it to the implemented OCIM flow without exposing or rewriting credentials.

06

Historical sandbox request succeeded

On August 12, Oracle accepted the OAuth exchange and a read-only OHIP request completed successfully in 921 milliseconds. This is historical evidence, not the August 24 result.

07

Fresh response validated

On August 24, the integration owner ran a new authenticated, read-only room-configuration request. The sanitized response was validated: 250 rows scanned, 250 flagged for review, and no writes.

08

Marketplace program enrollment approved

On August 25, Oracle approved and activated GlyphLock’s Cloud Services / Oracle Cloud Marketplace program enrollment 1655445. This is program enrollment, not a published NUPS listing or listing OCID.

09

Formal Simphony request submitted

On August 25, GlyphLock submitted the Simphony Integration Partner Program request. Oracle’s Partner Integration Team is reviewing active OPN standing and the request, with follow-up stated within 10 business days.

Next phase

Complete Oracle-controlled gates before production work

Marketplace publisher account

Confirm whether the Oracle Cloud Marketplace Publisher Account is active under the newly approved program enrollment; do not treat program enrollment alone as publisher activation.

NUPS listing package

Prepare and submit claims-safe product copy, public legal URLs, support details, sanitized screenshots, pricing posture and the preferred custom suffix glyphlock-nups. Record a listing OCID only after Oracle issues one.

Authorized customer environment

Obtain an authorized OPERA Cloud customer environment before planning controlled read-only production validation.

Simphony review & onboarding

Wait for Oracle’s Partner Integration Team to decide the submitted request and provide onboarding steps. Solution Validation, Marketplace publication and go-live remain future gates.

GlyphLock NUPS × Oracle OHIP

Evidence-backed Partner Sandbox integration milestone.