CUSTOM APPLICATION SSO

Give every application the same enterprise identity foundation.

Use Rainbow Secure’s web-based HTTP GET/POST integration to connect compatible applications regardless of programming language. Add rSecureKey MFA, unified user identity, centralized group-based access management, and consistent audit evidence across cloud-hosted, vendor-provided and on-premises applications.

Discuss your custom application → See the integration model

Technology independent
HTTP GET/POST
Web-based integration
On-premises and cloud

web-auth-request

                        // Any compatible web application
                        GET / authentication-request
                        POST / verification-response
                        {
                          authenticate: "rSecureKey",
                          identity: "unified",
                          access: "group-based",
                          evidence: "centralized"
                        }

✓ Identity verified ✓ Group access evaluated

THE CUSTOM-APPLICATION GAP

Your in-house applications should not become identity-security exceptions.

Local credential stores

Application-specific usernames, password hashes and recovery processes increase security and maintenance responsibility.

Repeated authentication code

Every development team can implement sign-in, MFA, authorization and failure handling differently.

Fragmented user access

Users and groups may be recreated inside every application, slowing access changes and offboarding.

Inconsistent evidence

Different logs and retention practices make investigation, reporting and audit preparation harder.

ONE IDENTITY LAYER

Bring SaaS and custom applications into one governed access model.

Rainbow Secure becomes the coordinated identity entry point while each application continues to enforce its approved business permissions.

rSecureKey MFA

Bring patented multidimensional authentication into supported custom-application sign-in journeys.

Unified user identity

Use one governed Rainbow Secure identity across SaaS, internally built and vendor-provided applications.

Group-based access

Assign application access through centralized users and groups instead of separate local entitlement lists.

Central audit evidence

Capture standardized authentication, assignment and access activity for reporting and review.

REFERENCE ARCHITECTURE

Move authentication out of application silos.

The application uses standard web requests to redirect or invoke Rainbow Secure authentication, receive the verified identity and evaluate assigned access. Because the integration uses HTTP GET/POST flows, it is not restricted to a specific programming language. Request validation, transport security, response handling, session and authorization responsibilities are confirmed during technical discovery.

Target architecture: Once migration and recovery testing are complete, the application no longer needs to maintain its own primary end-user password store. Temporary fallback or service credentials must be explicitly inventoried and governed.

User Requests application → Compatible web app Cloud · on premises · vendor → GET/POST · MFA · Identity · Groups → Authorized session Logged and reviewable

APPLICATION ENVIRONMENTS

Support the applications you build, host or inherit.

Rainbow Secure’s integration is based on web-accessible HTTP GET/POST request and response flows, not on one programming language. Any compatible application that can securely initiate the required request and process the approved response can be assessed. .NET, Java and PHP are examples our clients have already integrated.

Web-based applications

Connect compatible applications built with modern or legacy web technologies through the approved HTTP request flow.

Technology-independent approach

Cloud-hosted applications

Apply the same identity foundation to custom workloads hosted in Azure, Google Cloud, AWS or another supported environment.

Cloud deployment

On-premises applications

Integrate internal applications when their network and browser journey can securely reach Rainbow Secure services.

On-premises deployment

Vendor-provided applications

Connect third-party or customized software when the vendor allows the required web authentication request and response handling.

Vendor cooperation required

INTEGRATION JOURNEY

From local login to governed identity.

01 Discover
Map users, local credentials, roles, sensitive actions, hosting, recovery and audit requirements.
02 Design
Define the approved GET/POST flow, request validation, identity, session and authorization boundaries.
03 Integrate
Connect the application to Rainbow Secure authentication, users, groups and evidence services.
04 Validate
Test successful and failed sign-in, role changes, offboarding, timeout, recovery and logging.
05 Migrate
Move approved users from local authentication and retire redundant credential handling when safe.

CENTRALIZED GROUP ACCESS

Assign access once. Apply it consistently.

Map Rainbow Secure groups to the approved application and business roles. Joiner, mover and leaver changes can then flow through a central access model instead of requiring developers or application owners to update users manually in every system.

Department and team assignments
Application and role mapping
Permanent or time-bound access
Central removal and offboarding
Individual authentication accountability

VALUE FOR DEVELOPMENT TEAMS

Stop rebuilding identity plumbing in every application.

Less credential liability

Reduce the need to collect, hash, reset and protect end-user passwords inside each migrated application.

Less authentication code

Use an approved integration instead of independently creating MFA, recovery and sign-in policy logic.

Clear responsibility

Rainbow Secure handles the agreed identity services while the application retains business authorization and secure session responsibilities.

Faster security consistency

Apply the same Human-Verified authentication foundation across purchased SaaS and custom applications.

COMPLIANCE AND AUDIT EVIDENCE

Standardize what every connected application records.

Centralized authentication and access evidence helps security, compliance and application owners investigate activity and prepare reports across the connected application portfolio.

Rainbow Secure supports compliance and audit readiness; using the web integration does not automatically certify an application or organization.

Authentication event User · method · result · context

Access assignment Group · application · role · validity

Administrative change Actor · action · time · outcome

Reporting evidence Filter · review · export

RESPONSIBILITY MAP

A secure integration requires clear ownership.

Responsibility Rainbow Secure Application team

User authentication Provides the approved MFA and identity result Initiates the integration and handles outcomes securely

User and group identity Maintains governed identity and assignments Maps approved claims to application roles

Business authorization Can provide group and access context Enforces application permissions and sensitive actions

Session security Provides agreed authentication context Protects cookies, tokens, timeout and logout behavior

Evidence Records centralized identity and access activity Preserves application and business-event evidence

CUSTOM APPLICATION FAQ

Questions to resolve before integration.

Which application technologies can integrate?+

The integration is not limited to .NET, Java or PHP. It uses web-based HTTP GET/POST flows, so any compatible cloud or on-premises application that can securely make the required request and process the response can be assessed. .NET, Java and PHP are successful client examples.

Is this an SDK or a web API integration?+

Rainbow Secure provides a web-based integration pattern using HTTP GET/POST requests and responses. Implementation guidance and supporting SDK components help the application initiate authentication and securely process the result.

Can the application stop storing local passwords?+

That is the preferred target for migrated end-user authentication. Local credentials should be removed only after user mapping, recovery, service accounts, fallback access and rollback procedures are validated.

Does Rainbow Secure control every application permission?+

Not automatically. Rainbow Secure can centralize users, groups and application assignments. The custom application must securely map that identity context to its own business roles and permissions.

Can we add rSecureKey without implementing complete SSO?+

A supported user-verification or MFA flow may be integrated for a specific login or sensitive action. The exact GET/POST journey depends on the application and approved integration design.

Does this work for on-premises applications?+

Yes, when the application and user environment can securely reach the required Rainbow Secure services and the integration design satisfies networking, transport, request validation, session and recovery requirements.

What should a proof of concept test?+

Test request and response validation, identity matching, rSecureKey completion, group and role mapping, failure handling, session behavior, offboarding, recovery and audit events.

CONNECT YOUR CUSTOM APPLICATION

Secure the applications you build—not only the SaaS applications you buy.

Bring one representative application, its technology stack, hosting model, current login, user population, roles and audit needs. We will map the right first integration.

Request an integration assessment → Explore SaaS Application SSO