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:
×miniOrange supports Single Sign-On for secure login for users and admins. miniOrange supports several different protocols for your applications, such as SAML, WS-FED, OAuth, OIDC, JWT, RADIUS, etc. Using Single Sign-on, users can use one set of credentials to log in to multiple applications. This improves security, as it reduces avenues for phishing attacks, and also improves access to your applications.
miniOrange provides Single Sign-on for Mobile applications and Javascript framework based applications through JSON Web Token [so, JWT apps]. This solution allows you to setup Single Sign-On (SSO) into your applications that do not support the SAML 2.0 standard. You can allow your users to Single Sign-On into your application by verifying their Identity with your existing SAML 2.0 compliant Identity Provider. This is done using JSON Web Tokens (JWTs), and they can be easily integrated with your application built in any framework or language. You can add JWT apps to enable SSO in any mobile/client-side apps which do not support any standard protocols and are built on platforms like React.js, Firebase, Cordova, Angular.js, etc. You can also add Password-Less app links to the user portal from here.
Display Name | Enter the Display Name (i.e. the name for this application) |
Redirect URL | Enter the Redirect URL (i.e. the endpoint where you want to send/post your JWT token). You can add multiple redirect URLs by separating them with a ‘;’.E.g. abc.com;xyz.com |
Client ID | The Client ID is shown in the field below. Click the clipboard icon to copy it. |
Client Secret | Client Secret is hidden by default. Click the eye icon to reveal it and use the clipboard icon to copy it. This is used in the HS256 signature algorithm for generating the signature. |
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. |
Access Token | Enter the access token that will be sent to your redirect URL after a user logs in. This token helps your app know the user is allowed to access certain features. |
ID Token Expiry (In Mins) | Set how long (in minutes) the ID token will be valid. After this time, the user will need to log in again to get a new token. |
Subject | Choose what information, like the user’s email address, will be used to identify them in the token. This helps your app know which user is logged in. |
Signature Algorithm | Select your signature algorithm from the dropdown. |
The Logout URL of your application | Enter the web address where users should be sent after they log out. |
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.] |
Force Authentication | If you enable this option, users will have to log in every time, even if their session already exists. |
Enable User Mapping | Enable this option, if you want the app to show which user is signed in when it responds. |
Show On End User Dashboard | Enable this option if you want to show this app in the end-user dashboard. |