E-NUM - is a system used to log in to closed online resources. E-NUM provides extra protection with a security key (unique code book) stored on the user's mobile device.

You can easily integrate the E-NUM authorization on your resource.

There are two ways of integration: OAuth2 and Soap.

OAuth 2.0 allows third parties access to secured resources without providing them with the user's authentication details such as challenge-question/challenge-answer.

E-NUM supports the OAuth 2.0 standard specification.

Instruction on how to authorize on the bank website using ENUM.

Flow chart explaining in detail how to authorize on the bank website using E-NUM (top down)

1. A client of the bank requests access to the secured online-banking area
2. In order to grant access the bank redirects the client to the E-NUM system website so that he/she may complete authorization
3. In case the authorisation is successful, the E-NUM system will provide a one-time code to the client
4. In turn, the client's browser will transmit the authorization code to the bank's website
5. The bank website uses the authorisation code to request E-NUM to provide a temporary access token
6. This access token is then used to access API E-NUM methods which provide client identification.

• Authorization code request
• Authorization code response
• Access token request
• Access token response
• Getting the user identification details

Authorization code request

curl -i "https://auth.e-num.com/OAuth/Authorize?client_id=cd2068a8-cb18-4d24-bc85-dab0b3d3baf7&redirect_uri=https%3A%2F%2Fenumdemobank.e-num.com%2Fsignin-enum&scope=email%20phone&response_type=code&state=random-state"
HTTP/1.1 302 Found
Location: https://auth.e-num.com/Account/Login?ReturnUrl=%2FOAuth%2FAuthorize%3Fclient_id%3Dcd2068a8-cb18-4d24-bc85-dab0b3d3baf7%26redirect_uri%3Dhttps%253A%252F%252Fenumdemobank.e-num.com%252Fsignin-enum%26scope%3Demail%2520phone%26response_type%3Dcode%26state%3Drandom-state
                    

Authorization code response

GET https://enumdemobank.e-num.com/signin-enum?code=db8cea2e8bea4328b1ed&state=random-state
                    

Access token request

curl -i -d "client_id=cd2068a8-cb18-4d24-bc85-dab0b3d3baf7&client_secret=0e919552-1122-3344-5566-197f151bc349&redirect_uri=https%3A%2F%2Fenumdemobank.e-num.com%2Fsignin-enum&grant_type=authorization_code&code=db8cea2e8bea4328b1ed" "https://auth.e-num.com/OAuth/Token"
HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
{
    "access_token":"2YotnFZFEjr1zCsicMWpAA",
    "token_type":"bearer",
    "expires_in":900,
    "refresh_token":"tGzv3JOkF0XG5Qx2TlKWIA"
}
                    

Access token response

Getting the user identification details

$ curl -i -H "Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA" "https://auth.e-num.com/Api/Me"
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{"email":"test@example.com","phone":"00000000000"}
                    

Soap integration method requires the redirection of a client for the first time only to https://auth.e-num.com. All subsequent requests do not require redirection.

Driving authorization system using E-NUM by Soap method.

• A user of an external website enters his/her email address. The website backend requests the GetChallenge2 method of E-NUM service (the soap interface) for receiving a challenge-question.
• The website displays a challenge-question and asks a user to enter a challenge-response. The user response is checked with the CheckUserAnswer method.
• At his/her first attempt to log into the website, a user will be redirected to https://auth.e-num.com to authorize the use of E-NUM on the website by his/her account.

To start using this authorization method a website owner should register his/her website via https://e-num.com/Account/Consumers.

The http://service.e-num.com/Soap.asmx web service provides the basic methods: GetChallenge2 and CheckUserAnswer.

The GetChallenge2 method (receiving a challenge-question)

The CheckUserAnswer method (answer check)

...
<form id="login" method="post">
    ...
    <input type="text" name="response" id="response" />
    ...
</form>
...
<script src="https://signalr2.enum.ru/js/jquery.min.js"></script>
<script src="https://signalr2.enum.ru/js/signalr.min.js"></script>
<script>
    $(function () {
        // here it is necessary to pass the parameter obtained from the GetChallenge2 method
        var sessionId = '<%= SessionId %>';
        var connection = new signalR.HubConnectionBuilder()
            .withUrl('https://signalr2.enum.ru/autoResponseHub?sessionId=' + sessionId, {
                skipNegotiation: true,
                transport: signalR.HttpTransportType.WebSockets
            })
            .build();
        connection.on('response', function (response) {
            if ($.trim(response) !== '') {
                $('input#response').focus();
                $('input#response').val(response);
                $('form#login').submit();
            }
        });
        connection.start();
    });
</script>

A demonstration of the authorization procedure using E-NUM OAuth2 method and a fictitious bank.

Go to demonstration (working example)

Source code of the demonstration

You can implement your OAuth2-client E-NUM (in accordance with the description of the API methods above) or use ready clients libraries for your platform.

A libraly for Microsoft ASP.NET + Owin.

PHP example.

An example of the integration of E-NUM authorization Soap-method.