Need Help? We are right here!
Thanks for your Enquiry.
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:
×PL/SQL Application SSO (Single Sign-On) integration enables seamless authentication in PL/SQL-based applications using header-based SSO. Users can log in with their existing credentials through LDAP, AD passwords, or other Identity Providers (IDPs). By configuring an appropriate IDP such as miniOrange, Azure AD, Okta, or a custom solution, the authentication process is handled, and an authentication token is issued. This token is passed in the headers of each request and undergoes validation to ensure its authenticity and integrity. This extracts user information from the validated token, including user ID, roles, and permissions which enables the implementation of access control mechanisms. By following this process, SSO can be effectively implemented in PL/SQL applications, delivering a streamlined and secure authentication experience while simplifying login, reducing credential management, and enhancing overall application security.
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, OpenLDAP, AWS etc), Identity Providers (like Microsoft Entra ID, Okta, AWS), and many more. You can configure your existing directory/user store or add users in miniOrange.
miniOrange offers 1 hour free help through a consultation call with our System Engineers to Install or Setup PL/SQL SSO SAML solution in your environment with 30 days free trial. For this, you need to just send us an email at idpsupport@xecurify.com to book a slot and we'll help you setting it up in no time.
Basic Tabs | Description |
---|---|
Display Name | Enter the Display Name (i.e., the name for this application). |
Redirect URL | Copy the Redirect-URL from PL/SQL Application. You will get this URL when you create an application in the PL/SQL admin console. |
Client ID | You can find Client ID by clicking the icon as shown below. |
Client Secret | You can find Client Secret by clicking the icon as shown below. |
Description (Optional) | Add a description if required. |
Upload App Logo (Optional) | Upload an app logo (Optional). The app will be shown in the end-user dashboard with the logo that you configure here. |
Group Name | Select the group for which you wish to add a this policy. For multiple groups, you can click here to add a multiple/separate policies for each group. |
Policy Name | You can give a name for the authentication policy. |
First Factor | Select the login method as Password and Password-less. You can enable 2-Factor Authentication (MFA), Adaptive Authentication and Force MFA On Each Login Attempt if required. |
Primary Identity Provider | Select the default ID source from the dropdown for the application. If not selected, users will see the default login screen and can choose their own IDP. [Choose miniOrange in this case.] |
SSO FLows | Select the desired SSO flow from the dropdown, such as miniOrange as IDP, miniOrange as Broker, or miniOrange as Broker with Discovery Flow. |
Show on Enduser Dashboard | Enable this option if you want to show this app in the end-user dashboard. |
Force Authentication | If you enable this option, users will have to log in every time, even if their session already exists. |
Allowed Logout URIs | Click the Allowed Logout URIs link to add a list of post-logout redirect URIs. Users will be redirected to one of these URIs after a successful logout from miniOrange. |
Single Logout Enabled | Enable this option to send logout requests to other applications when logging out from this app. |
Sign in URL | You can include user attributes in the sign-in URL using placeholders like {{username}}, {{primaryEmail}}, {{customAttribute1}}, etc. These placeholders will be dynamically replaced with the actual user values during the IdP-initiated SSO flow. You can generate url using following attributes: username, primaryEmail, alternateEmail, fname, lname, primaryPhone and customAttribute1. The url could be like this https://<sso-url>>?username={{username}}
https://<sso-url>>?username={{username}}&email={{primaryEmail}} https://<sso-url>>/{{customAttribute1}}/{{customAttribute2}}/?username={{username}} |
Authorization Endpoint: | https://login.xecurify.com/moas/idp/openidsso
(Note: Use this endpoint only if you want to use miniorange as oauth identity server.) https://login.xecurify.com/moas/broker/login/oauth/260174 (Note: Use this endpoint only if you are configuring any Identity Provider in Identity Providers Menu and not using miniorange as IDP.) |
Token Endpoint: | https://login.xecurify.com/moas/rest/oauth/token |
User Info Endpoint: | https://login.xecurify.com/moas/rest/oauth/getuserinfo |
Introspection Endpoint: | https://login.xecurify.com/moas/rest/oauth/introspect |
Revoke Endpoint: | https://login.xecurify.com/moas/rest/oauth/revoke |
OpenID Single Logout Endpoint: | https://login.xecurify.com/moas/idp/oidc/logout?post_logout_redirect_uri= |
email : | View email address of the user |
profile : | View profile attributes of the user account |
openid : | Retrieve JWT token for OpenID Connect |
dads.conf
<Location /pls/first>
SetHandler pls_handler
Order allow,deny
Allow from All
AllowOverride None
PlsqlDatabaseUsername <admin_username>
PlsqlDatabasePassword <admin_password>
PlsqlDatabaseConnectString localhost:1521:orcl SIDFormat
PlsqlAuthenticationMode CustomOwa
PlsqlCGIEnvironmentList MO_REMOTE_USER
</Location>
OWA_Custom_body
create or replace package body OWA_CUSTOM is
function authorize return boolean is
begin
owa_sec.set_protection_realm('first');
return TRUE;
end;
begin
owa_sec.set_authorization(OWA_SEC.CUSTOM);
end;
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.
Attribute | Description |
---|---|
Activate LDAP | All user authentications will be done with LDAP credentials if you Activate it |
Fallback Authentication | If LDAP credentials fail then user will be authenticated through miniOrange |
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 |
Sync users in miniOrange | Users will be created in miniOrange after authentication with LDAP |
Attribute Name sent to SP = organization
Attribute Name from IDP = company
Set up AD as External Directory configuration is complete.
Note: Refer our guide to setup LDAP on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.
Contact Us to get the miniOrange Oracle PL/SQL SAML SSO (Single sign-on) Connector module.
A. Restricting access to PL/SQL with IP Blocking
You can use adaptive authentication with PL/SQL Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.
You can configure Adaptive Authentication with IP Blocking in following way:Attribute | Description |
---|---|
Allow | Allow user to authenticate and use services if Adaptive authentication condition is true. |
Challenge | Challenge users with one of the three methods mentioned below for verifying user authenticity. |
Deny | Deny user authentications and access to services if Adaptive authentication condition is true. |
Attribute | Description |
---|---|
User second Factor | The User needs to authenticate using the second factor he has opted or assigned for such as |
KBA (Knowledge-based authentication) | The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further. |
OTP over Alternate Email | User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further. |
B. Adaptive Authentication with Limiting number of devices.
Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.
You can configure Adaptive Authentication with Device Restriction in following wayC. Add Adaptive Authentication policy to PL/SQL.
D.Notification and Alert Message.
This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :
Option | Description |
---|---|
Challenge Completed and Device Registered | Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device. |
Challenge Completed but Device Not Registered | Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device. |
Challenge Failed | Enabling this option allows you to send an email alert when an end-user fails to complete the challenge. |