• Home
• Content Library
• Admin Docs
• Configure Application
• How to add a JWT App

How to add a JWT App

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 login to multiple applications. This improves security, as it reduces avenues for phishing attacks, and also improves access to your application.

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 which do not support SAML 2.0 standard. You can allow your users to Single Sign-On into your application by verifying Identity with your existing SAML 2.0 compliant Identity Provider. This is done using JSON Web Token (JWT) tokens and it can be easily integrated with your application built in any framework or language. You can add JWT app to enable SSO in any mobile/client-side apps which do not support any standard protocols and built on platforms like React.js, Firebase, Cordova, Angular.js, etc. You can also add Password-Less app links to user portal from here.

Configure Single Sign-On (SSO) Settings for JWT Apps:

• Login into miniOrange Admin Console.



• Click on Apps. It shows a list of all configured applications and option to modify them. Click on Add Application.



• Under Choose Application, select JWT from the All Apps dropdown.



• Search for your application from the list, if your application is not found. Search for jwt and you can set up your app via JWT App.



• You can configure the following details in the application:

APP Name	Enter the API Name (i.e. the name for this application), and add a description if required.
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
Identity Source	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.You can select ‘miniOrange’ here as users will be authenticated from the default DB.
Upload an 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.
Login Method	Select the login method as Password. You can enable 2-Factor and Adaptive Authentication.
Show On End User Dashboard	Enable this option if you want to show this app in the end-user dashboard.

 


• Click on Edit in the select menu against your app, to get further details about your recently added JWT application.




Client ID	If your application provides its own client ID, you can configure it by clicking on the Customize button.
App Secret	You can find App Secret by clicking on the icon as shown below. This is used in the HS265 Signature algorithm for generating the signature.
Signature Algorithm	Select your signature algorithm from the dropdown.
Identity Source	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.]
Redirect URL	Given below is your app URL where you will receive your token. RSA 256 : <your_app-login-url> (Here token will be added by the system) HS256 : <app-login-url/?id_token=>

• Signature Algorithms for JWT
• RSA-SHA256
  • Asymmetric, uses a set of private and public keys to generate and validate the signature which is included in the JWT token.
  • The private key is used to generate the signature on the IDP side.
  • The public key is used to verify the signature on the SP side.
  • We provide the public key for this.
• HS256
  • Symmetric, uses the same secret key to generate and validate the signature
  • The secret key in this case is configurable from the app configuration page.
• Endpoints:
• Single Sign-On URL:
  • This URL is used to initiate user authentication to obtain the JWT token.
  • Take redirect_uri as one of the query parameters.
  • After successful authentication on the IDP end, an active user session is created in the IDP and the user is redirected to the redirect_uri with the JWT token.
• Single Logout URL:
  • This URL is used to log out the user from the IDP by removing the active user session.
  • Take redirect_uri as one of the query parameters.
  • After removing the active user session, the IDP redirects the user to the redirect_uri.
• Reply back URL for IdP initiated logout:
  • This URL is used to initiate the logout in case the JWT user login was IDP Initiated [User logged in to the dashboard
    first and then initiated the login for the app from the dashboard.]
  • After logging out the user from the IDP, the user is redirected to the IDP dashboard login page.