Getting an access token

Gurtam team has created a more secure way of authorization similar to oAuth. The previous core/login way of authorization was valid until 01 Oct 2015. All clients who implemented their own login forms or demo access links should change them to correspond to the new authorization way.

For now, two forms exist: an extended and a simplified one.

The extended form is generally useful for mobile and other apps.

http://<host>/login.html

http://<host>/login.html?client_id=...&access_type=...&activation_time=...&duration=...&lang=...&flags=...&user=...&redirect_uri=...&response_type=...&css_url=...

All the parameters are optional.

After successful authorization, a redirect to redirect_uri occurs, and the following GET-parameters are transferred:

• access_token (72-symbol token which may be used for authorization in future);
• user_name (authorized username, if 0x1 flag was stated before token generation).

In case of an authorization error, a redirect occurs to the login form itself, the specified error is shown and the following GET-parameters are transferred:

• svc_error (error code);
• client_id;
• access_type;
• activation_time;
• duration;
• flags.

After getting a 72-symbol token, you can use it in your apps for authorization with the method token/login:

svc=token/login&params={"token":"<access_token>","operateAs":"<optional_sub_user>"}

The number of tokens per user is limited to one thousand.

The form is used for simple embedding into sites via iframe to quickly access one or more monitoring sites after authorization. By default, a link to the monitoring site will be created. Also, you may add links to other sites (using cms_url, mobile_url, demo_url).

http://<host>/login_simple.html

http://<host>/login_simple.html?lang=...&cms_url=...&cms_title=...&lite_url=...&mobile_url=...&demo_title=...&demo_url=...&title=...&css_url=...

All the parameters are optional.