Single Sign-On (SSO) removes the need to repeatedly type usernames and passwords, which increases productivity and prevents many types of online fraud that is caused by using same or similar passwords across apps, tying in passwords in un-safe environments, password sharing etc.

miniOrange Single Sign-On APIs allows you to integrate sso quickly and secure access to your applications.


  • You need to create a free trial account with miniOrange.
  • You should have an account of application where you want to single sign on into.

Steps to integrate miniOrange Single Sign on API for OpenID Connect

Step 1: Create a REST service or similar on your application to handle response from Authorization Endpoint

Note : this must be the redirect URI parameter.

Example (https://<your-domain>/rest/openidresponse)

  • Response attributes: code ,state.

Now you just need to make two calls: one to get access token and another to get user info with the help of that access_token.

     //Import our miniOrange API(copy all the JAR files in a lib folder and add them to build path)
     //Step 1 : Make a token request using code and state parameter received on the redirect uri.

         String token = AuthServerRequest.sendTokenRequest(code, state);
     Example string token JSON :

     //Step 2 : OPTIONAL. Validate id_token on your side.
     <Your java code for validating id_token from the JWK set>

     //Step 3: Make a user_info request. Fetch access_token from the JSON string token received in Step 1.

       String user_info = AuthServerRequest.sendUserInfoRequest(access_token);

     Example user info JSON :
     "email":"demo@miniorange.co.in","name":"Demo User","family_name":"User",

         Return user_info; //Proceed your login flow with the user_info scopes.

token is a JSON which contains the following attributes:

Field Description
access_token OAuth 2.0 Access Token. This is returned from the token endpoint
token_type OAuth 2.0 Token Type value. The value MUST be Bearer or another token_type value that the Client has negotiated with the Authorization Server. Clients implementing this profile MUST support the OAuth 2.0 Bearer Token Usage [RFC6750] specification. This profile only describes the use of bearer tokens. This is returned in the same cases as access_token is.
expired_in OPTIONAL. Expiration time of the Access Token in seconds since the response was generated.
scope scope parameter value : openid
id_token Contains a JSON of fieldset iss, sub ,aud, nonce, exp, iat, auth_time, at_hash

id_token contains the following JSON attributes:

Field Description
iss https URI that indicates the issuer
sub identifier of the user at the issuer
aud client_id of the requesting client
nonce the nonce parameter value received from the client
exp expiration time of this token
iat time when this token was issued
auth_time time the authentication happened
at_hash the first half of a hash of the access token

User info is a JSON which contains the following attributes:

Field Description
Email Email of the user
Phone Contact number of the user
Name Full name of the user

Once you have the user info JSON. You can initiate your login by passing the email/username information to your local authentication functionality.

Endpoints Explained

If you wish to use any third party client libraries. Or if want to write your own client, than you can use our Endpoint's directly to authenticate user in your website or application.

Discovery End point Service: Contains URL and information of all the endpoint's mentioned below including path to JSON JWK set.


Authorization endpoint

The authorisation endpoint is the only one where the end-user interacts with the OpenID Connect provider. The other endpoints are meant for handling direct back - channel requests from the client application.

  • Request params : client_id, scope, redirect_uri, response_type, state.

  • Client_id : Unique client identifier

  • Scope: Kind of information required for a particular user.

  • Redirect_uri : https endpoint to which the user should be returned.

  • Reponse : code, state

    Sample Request:

    Sample Response:
        code: kuwbrec8_sacca
        state: yAwL-57K10sIIpGeVO7nR7ZAnzdsj01uGothExyVpmo

Token End point Service

The token endpoint authenticates the client application, then lets it exchange the code received from the authorisation endpoint for an ID token and access token.

Token uri from discovery endpoint

  • Request params : code, state

  • Request Type: POST

  • Response : token (JSON)

Userinfo Service

The UserInfo endpoint is an OAuth 2.0 protected HTTPS resource for which an access token is required. The UserInfo endpoint returns consented profile information to the client application. This information is intended to facilitate user provisioning.

  • URL : userinfo uri from discovery endpoint

  • Request params : Header : Bearer {access_token}

  • Request Type: POST

  • Response : user_info (JSON)

Provider JWK Set Endpoint

The JWK endpoint contains keys to sign and validate the id_token on server and client side respectively.

  • URL : Jwk set uri from Discovery endpoint

  • Request Type: POST

  • Response : JWK set (JSON)

miniOrange OpenID Connect Client Library Documentation for Java

miniOrange client library can be used to request/make calls to our token endpoint and user info endpoint.

  • Token endpoint:

  • Request : code, state.

  • Response : token JSON: { 'aud': xxx, 'sub': xxx, 'iss': xxx, 'exp' : xxx, 'access_token': xxx }

  • User info endpoint:

  • Request: access_token

  • Response : userinfo JSON {'name' : xxx, 'email' : xxx , 'primaryPhone' : xxx }

  1. Calling token endpoint.

token = AuthorizationServerRequest.sendTokenRequest(code, state);

  1. Calling user info endpoint.

user_info = authorizationServerRequest.sendUserInfoRequest(access_token);

Token and user_info are the JSON objects containing access_token and user information respectively.

Libraries JAR

  • Main library: miniorange-openid-api

  • Assisting libraries required:

    • commons-httpclient 3.1
    • commons-lang3-3.4
    • commons-logging-1.1.2
    • guava-12.0.1
    • httpclient-4.1.1
    • http-core-4.1
    • json20090211