Need Help? We are right here!
Oracle DB is database which uses techniques to provide security to site-to-site connections. Also, it secures a point-to-point connection. You can enable two-factor authentication (2FA) for your change to Oracle DB with Active Directory as a user store to increase security level. When you enable 2FA, your users enter their username and password (first factor) as usual, and as a second factor they have to enter an authentication code which will be shared virtually on their device or in the form of a hardware token. This 2FA/MFA solution adds an additional security measure to prevent unwanted users getting access to your Oracle DB .
The 2-factor authentication can be of two types depending on the applications.
miniOrange accomplishes this by acting as a RADIUS server that accepts the username/password of the user entered as a RADIUS request and validates the user against the user store as Active Directory (AD). After the first level of authentication, miniOrange prompts the user with 2-factor authentication and either grants/revokes access based on the input by the user.
miniOrange supports multiple 2FA/MFA authentication methods for Oracle DB secure access such as, Push Notification, Soft Token, Microssoft / Google Authenticator etc.
|miniOrange Authenticator||Soft Token|
|miniOrange Push Notification|
|Mobile Token||Google Authenticator|
|SMS||OTP Over SMS|
|SMS with Link|
|OTP Over Email|
|Email with Link|
|Call Verification||OTP Over Call|
|Hardware Token||Yubikey Hardware Token|
|Display Hardware Token|
You can opt for any of the 2FA methods to secure your Oracle DB . To integrate 2FA, you can enable RADIUS authentication in Oracle DB and configure policies in miniOrange to enable or disable 2FA for users.
miniOrange provides user authentication from various external directories such as miniOrange Directory, Microsoft AD, Azure Active Directory/LDAP, AWS Cognito and many more.
Can't find your Directory? Contact us on firstname.lastname@example.org
|Client Name:||Any name for your reference.|
|Client IP:||IP address of VPN server which will send Radius authentication request.|
|Shared Secret:||Security key.
For Eg. "sharedsecret"
(Keep this with you, you will need to configure same on VPN Server).
|Include Password & OTP in same Request||Check this option for clients which takes password and the OTP in same request. Otherwise keep it unchecked.|
|Send Groups in Response||Enable this to send user groups as Vendor-Specific Group Attributes.|
|Vendor Name||Group Attribute||Vendor ID||Vendor Attribute ID|
|Cisco ASA VPN||26 Vendor-Specific||3076||25|
|Fortinet VPN||26 Vendor-Specific||12356||1|
|Palo Alto VPN||26 Vendor-Specific||25461||5|
|SonicWall VPN||26 Vendor-Specific||8741||3|
|Citrix VPN||26 Vendor-Specific||66||16|
|Group Name:||Group for which the policy will apply.|
|Policy Name:||Any Identifier that specifies policy name.|
|Login Method||Login Method for the users associated with this policy.|
|Enable 2-Factor Authentication||Enables Second Factor during Login for users associated with this policy.|
|Enable Adaptive Authentication||Enables Adaptive Authentication for Login of users associated with this policy.|
Only For On-Premise Version
Open Firewall Ports.
|Port:||Specifies the listening port of the primary RADIUS server. The default value is 1645.|
|Timeout (seconds):||Specifies the time the Oracle database server waits for a response from the primary RADIUS server. The default is 15 seconds.|
|Number of Retries:||Specifies the number of times the Oracle database server resends messages to the primary RADIUS server. The default is three retries.|
|Secret File:||Specifies the location of the secret key on the Oracle database server. The field specifies the location of the secret key file, not the secret key itself.|
CONNECT system@database_name; Enter password: <password> CREATE USER username IDENTIFIED EXTERNALLY; GRANT CREATE SESSION TO USER username; EXIT
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.
1. Create User in miniOrange
2. Bulk Upload Users in miniOrange via Uploading CSV File.
Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.
|Activate LDAP||All user authentications will be done with LDAP credentials if you Activate it|
|Sync users in miniOrange||Users will be created in miniOrange after authentication with LDAP|
|Backup Authentication||If LDAP credentials fail then user will be authenticated through miniOrange|
|Allow users to change password||This allows your users to change their password. It updates the new credentials in your LDAP server|
|Enable administrator login||On enabling this, your miniOrange Administrator login authenticates using your LDAP server|
|Show IdP to users||If you enable this option, this IdP will be visible to users|
|Send Configured Attributes||If you enable this option, then only the attributes configured below will be sent in attributes at the time of login|
Refer our guide to setup LDAPS on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
(The Active Directory Group Provisioning (Sync) setup is done. Now, whenever a user is created or modified in LDAP server and if the Assign Users to groups is enabled, then user group attribute from the LDAP server will be automatically synced and the user group will be assigned or changed accordingly in miniOrange.)
(You can follow these steps and use the login URL present in the Branding section.)
Our Other Identity & Access Management Products