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:
×The miniOrange identity provider (IdP) is a service that stores and verifies user identity. IdPs are typically cloud-hosted services, and they often work with single sign-on (SSO) providers to authenticate users. The purpose of this guide is to get you up and run as quickly as possible so that you can play with and test-drive various features that miniOrange has. It is a standalone application with default database and packaged tomcat and does not cover any complex deployment options. We support both windows and linux os for installation.
This short tutorial walks you through starting up the server in standalone mode, setting up the initial admin account, and logging into the miniOrange admin dashboard.
miniOrange On-Premise server has the following system requirements. This section lists recommended versions and requirements.
Operating System (Linux preferred) |
Any operating system that runs minimum Java 8 |
CPU Core | 4 Core |
RAM | 16GB and above |
RAM | 16GB and above |
HDD | 20GB or above |
JAVA Environment | jdk1.8.0_381 and above |
Server Access Policies | Port 80 (HTTP Port) Port 1812, 1813 (Radius UDP Port), RDP Port 3389(Windows Server)- For login, SSH Port(Linux Server)- For login |
Database | Find the list of all supported versions here. |
Server Ports | Ensure the following ports are available on the server for installing the required services: 6379 - Redis 5672 -RabbitMq |
You can download miniOrange On-Premise server from here
Follow the steps to deploy miniOrange On-Premise server on your operating system:
CertUtil -hashfile mo-idp-server-4.8.1-installer.exe SHA256
In case of no internet connectivity. You can choose and download the offline installer from here.
If you already have a database setup which is not in the list below, you can contact us to add support for that database.
ALTER DATABASE YourDatabaseName
SET ALLOW_SNAPSHOT_ISOLATION ON;
You can refer this link to know more about how miniOrange can enhance performance and data consistency by enabling Snapshot Isolation.
i. Modify the Server Base URL:
ii. Update Hosts File:
C:\Windows\System32\drivers\etc
Once the Java installation is complete, check that the JAVA_HOME environment variable has been set correctly.Open a command prompt and type echo %JAVA_HOME%
and hit Enter. If you see a path to your Java installation directory, the JAVA_Home environment variable has been set correctly. If nothing is displayed, or only %JAVA_HOME% is returned, you'll need to set the JAVA_HOME environment variable manually.
echo %JAVA_HOME%
echo %JRE_HOME%
> ...\bin\startup.bat
If you already have a database setup which is not in the list below, you can contact us to add support for that database.
ALTER DATABASE YourDatabaseName
SET ALLOW_SNAPSHOT_ISOLATION ON;
You can refer this link to know more about how miniOrange can enhance performance and data consistency by enabling Snapshot Isolation.
We assume the entire suite of services will be installed on a standalone system. In case of a distributed system setup you can reach out to us and our engineers will help you to install this in a distributed, Highly Available manner.
services/windows/
<miniOrange Directory\services\logs>
i. Modify the Server Base URL:
ii. Update Hosts File:
C:\Windows\System32\drivers\etc
a. Database Setup:
b. PostgreSQL Installation Guides:
c. Install RabbitMQ using the relevant guide:
d. To verify the RabbitMQ installation, use the following command:
systemctl status rabbitmq-server.service
e. Create a Database (PostgreSQL Example):
sudo -u postgres psql
create database <databasename>;
chmod +x mo-installer.sh
sudo sh mo-installer.sh
sudo systemctl start mo-idp-miniorange.service
Database Type | PostgreSQL/ MySQL/ MSSQL |
Database Host | localhost |
Database Username, Password, and Database Name | as set during installation |
/opt/mo-idp-server-4.8.1/moas/WEB-INF/classes/db.properties
. Copy the jdbc.url value./opt/mo-idp-server-4.8.1/services/config/application.properties
Properties | Values |
---|---|
MO_DB_PRIMARY_URL & MO_DB_REPLICA_URL | jdbc.url copied earlier |
MO_DB_PRIMARY_USER & MO_DB_REPLICA_USER | <database_username> |
MO_DB_PRIMARY_PASS & MO_DB_REPLICA_PASS | <database_password> |
sudo chmod +x start-services.sh
./start-services.sh
i. Modify the Server Base URL:
ii. Update Hosts File:
Issue: One or more services are not running.
Resolution:
Before moving forward, you need to make two changes related to same site cookie. Starting with version 80, Google Chrome will change the default value for the SameSite cookie parameter to Lax. Therefore, changes are required and SameSite parameter has to be set to NONE.
To do changes, follow the path: mo-idp-server-<version>/moas/WEB-INF/classes. In this folder search for the file spring-context-onpremise and open it in editor. Search for bean id="customCookie". you will see a bean with name samesite and secure properties. Update value of samesite from LAX to NONE and of secure to true.
keytool -genkey -alias onpremssoidp -keyalg RSA -keystore onpremssoidp.jks
1. Open Tomcat Configuration:
2. Edit server.xml:
<Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="<JKS Keystore Path>" ciphers="ALL" keystorePass="<Password while keystore generation>"/>
Note: Make sure the .jks file has appropriate permissions/run command prompt as Administrator.
Using a certificate from Trusted CAs like LetsEncrypt, GoDaddy, Comodo SSL.
certbot certonly --standalone -d.example.com
#:/etc/letsencrypt/live/example.com# ls
cert.pem chain.pem fullchain.pem privkey.pem README
<Connector port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" maxThreads="150" SSLEnabled="true"> <SSLHostConfig> <Certificate certificateFile="conf/cert.pem" certificateKeyFile="conf/privkey.pem" certificateChainFile="conf/chain.pem" /> <SSLHostConfig> <Connector>
keytool -genkey -alias onpremssoidp -keyalg RSA -keystore onpremssoidp.jks
keytool -delete -alias onpremssoidp -keystore onpremssoidp.jks
openssl pkcs12 -export -in <GoDaddyCertificate>.crt -inkey <PrivateKey>.key
-out <PublicPrivateKeyPair>.p12 -name tomcat -CAfile gd_bundle-g2-g1.crt -caname root
<Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="<JKS Keystore Path>" ciphers="ALL" keystorePass="<Password while keystore generation>"/>
Creating a New Keystore
keytool -genkey -alias server -keyalg RSA -keysize 2048 -keystore your_site_name.jks
Creating a CSR on Tomcat Servers
keytool -certreq -alias server -file csr.txt -keystore your_site_name.jks
How to Install an SSL Certificate on Your Tomcat Server
keytool -import -alias server -file your_site_name.p7b -keystore your_site_name.jks
Configuring Your SSL/TLS Connector
<Connector port="443" maxHttpHeaderSize="8192" maxThreads="100" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" SSLEnabled="true" clientAuth="false" sslProtocol="TLS" keyAlias="server" keystoreFile="/home/user_name/your_site_name.jks" keystorePass="your_keystore_password" />
mo-service.bat uninstall
If you encounter the error:"keytool error: java.lang.Exception: Key pair not generated, alias <onpremssoidp> already exists"
This indicates that the keystore file already exists. To resolve this, follow these steps:
Encounter the error:
If you get an error similar to the above image, follow these steps.
Disable IPv6 on Windows:
Our Other Identity & Access Management Products