Need Help? We are right here!
Thanks for your Enquiry. Our team will soon reach out to you.
If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com
Search Results:
×A step-by-step guide to installing and configuring miniOrange Access Gateway (MAG) for secure access and authentication.
miniOrange access Gateway server has the following system requirements.
Follow the steps to deploy the miniOrange Access gateway server on your operating system:
Download Required Files:
Download Required Files:
(Don’t have an account? No worries! Click here to create one.)
Note: Upstream Group contains the details of servers on which your application is deployed.
Group Name | Enter a unique name for the Group of Upstream Servers. |
Load Balancing |
|
Scheme | Select the scheme/protocol used to access the your Application Server. This field can only have one value either HTTP or HTTPS. |
Host | The FQDN or IP Address of your Application Server. |
Port | The Port on which the your Application Server is listening. |
Note: Load Balancing can only be enabled if at least 2 servers are enabled.
Note: Authentication Providers contain IDP configurations used for user authentication.
If SAML is Selected:
Note: miniOrange Access Gateway metadata will be provided per application.
If OAuth is Selected:
Note: If your application isn't listed, select Custom Application to configure it manually.
Application Name | Enter a unique name to identify Application. |
Hostname | FQDN on which this Access Gateway Application will be accessed. |
Server | Select the Access Gateway Server from the dropdown where you want to deploy the application. |
Request Caching | Enable or disable Request Caching. If enabled, specify the URL paths for which responses should be cached on the browser side. |
Note: The Hostname entered above must have a DNS entry pointing to the server on which miniOrange Access Gateway is deployed.
Path | Defines the request URL pattern (e.g. /jde/owhtml, /*) that this route will handle. Supports exact paths or wildcards. |
Interceptors | A list of interceptors that process the request before it's forwarded. You can add, remove, or reorder them. |
Authentication Provider Name | Select the name from the list of configured Authentication Providers . This option will be enabled only if SAMLAuth Interceptor is present. |
Upstream Group | Select the name from the list of configured Upstream Groups where the request should be forwarded. |
Predefined-Interceptor Type | Function |
---|---|
SAML | Forces SAML Authentication before forwarding the request to upstream server. |
Catch Cookies | Fetch cookies from the request and add these to the corresponding response from upstream server. |
Session Logout | Destroys the session of the user in Access Gateway |
Clear Cache | Disable Caching |
Note: Interceptors are components which act like filters, that process incoming requests before they are forwarded to the Upstream Server.
Interceptor Type | Function |
---|---|
Header | Adds headers to request as specified in the configuration. |
Redirect | Redirects to specified url instead of forwarding the request to upstream server. |
Request Verification | Performs actions based on the configured verifiers. |
JWT |
Must be used after an Authentication Interceptor (SAML/OAuth).
This interceptor generates a JWT token and appends it to the URL path where the interceptor is applied. |
HTTP | Enable this button if you want to allow Access Gateway to run on HTTP |
Port | Enter the Port number that the Access Gateway will listen on for HTTP Requests |
HTTPS | Enable this button if you want to allow Access Gateway to run on HTTPS |
SSL Port | Enter the SSL Port number that the Access Gateway will listen on for HTTPS Requests |
Keystore Type | Type of keystore used for SSL Certificates (JKS, PKCS12, PEM) |
Upload Keystore | If Keystore Type is JKS / PKCS12, then upload keystore files with extensions .jks, .p12, .pfx |
Upload PEM Certificate | If Keystore Type is PEM, then upload file with .pem extension |
Upload Private Key | If Keystore Type is PEM, then upload private key with .pem extension |
Note: After creating a server, go to the Applications section, click Edit on the desired application, and select the server where the application should be deployed.
On the Admin Dashboard, you can view configuration summaries, monitor server health status, and inspect live request traffic.
Note: Initially, a trial license valid for 15 days is provided. To upgrade the license, please Contact Us.