No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor 9000 V300R006C00 Object Storage Service (Compatible with OpenStack Swift APIs) Administrator Guide 07

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Interface Used by Third-Party Management Software to Log In to DeviceManager

Interface Used by Third-Party Management Software to Log In to DeviceManager

By clicking DeviceManager of the third-party management software, users are directed to the home page of DeviceManager without entering the user name or password.

Invoking methods of this login interface:

  1. The third-party management software needs to save the valid account information of DeviceManager (user name and password).
  2. With the information of this account, the third-party management software invokes https://IP:8088/deviceManager/v1/rest/xx/sessions and send requests to DeviceManager.

    IP indicates the management IP address of the OceanStor 9000.

    The request mode is POST. Table 19-2 describes the request message headers, and Table 19-3 describes the message parameters.

    Table 19-2  Headers of the request messages that request the token value

    Header

    Description

    Example

    Accept

    Specifies the content types that can be accepted by clients.

    Accept: text/plain, text/html

    Accept-Encoding

    Specifies the content compression encoding types returned by web servers and supported by clients.

    Accept-Encoding: gzip, deflate, sdch

    Accept-Language

    Specifies the languages supported by clients.

    Accept-Language: zh_CN,en

    Cache-Control

    Specifies the cache mechanisms of requests and responses.

    Cache-Control: no-cache

    Connection

    Indicates whether keepalive connection is required. (HTTP 1.1 uses keepalive connection by default.)

    Connection: keep-alive

    Content-Type

    Types of request contents sent from clients to servers.

    Content-Type: application/json; charset=utf-8

    Table 19-3  Parameters of the request messages that request the token value

    Parameter

    Description

    data

    {
        username:xxx,  //user name
        password:xxx,  //password
        scope:xxx  //authentication mode: The value is 0 or 1. 0 indicates local authentication, and 1 indicates domain authentication.
    }
    
  3. After receiving request messages, DeviceManager authenticates the account information.
  4. After the account information passes the authentication, DeviceManager returns a random token value to the third-party management software. The validity period for token is one minute.

    Table 19-4 lists the parameters of the response messages.

    Table 19-4  Parameters of the response messages that obtain the token value

    Parameter

    Description

    result

    //Result set type: Json object
    //Success:
    {
        error:{
            code:0,
            description: ''
        },
        data:{
            passphrase: 'xxx'  //token information
        }
    }
    
    //failure:
    {
        error:{
            code:xxx,
            description:'xxx'
        }
    }
  5. With the random token value and language information, the third-party management software redirects to https://IP:8088/deviceManager/devicemanager/feature/login/crossDomainLogin.html?passphrase=xxx&language=xxx.

    IP indicates the management IP address of the OceanStor 9000.

    The request mode is GET. Table 19-5 describes the request message headers, and Table 19-6 describes the message parameters.

    Table 19-5  Headers of the redirect request messages

    Header

    Description

    Example

    Accept

    Specifies the content types that can be accepted by clients.

    Accept: text/html

    Accept-Encoding

    Specifies the content compression encoding types returned by web servers and supported by clients.

    Accept-Encoding: gzip, deflate, sdch

    Accept-Language

    Specifies the languages supported by clients.

    Accept-Language: zh_CN,en

    Cache-Control

    Specifies the cache mechanisms of requests and responses.

    Cache-Control: no-cache

    Connection

    Indicates whether keepalive connection is required. (HTTP 1.1 uses keepalive connection by default.)

    Connection: keep-alive

    Content-Type

    Types of request contents sent from clients to servers.

    Content-Type: text/html; charset=utf-8

    Cookie

    Data stored on the user's local terminal.

    Cookie: CSRF_IBASE_TOKEN=XXXX(XXXX indicates the Token value); language=en; session=ismsession=null

    Table 19-6  Parameters of the redirect request messages

    Parameter

    Description

    passphrase

    The token value information obtained in 4.

    language

    • Chinese: language=zh
    • English: language=en
  6. After receiving the request, DeviceManager uses the token value for authentication.
  7. If the authentication succeeds, crossDomainLogin.html is returned, and users are automatically directed to the home page of DeviceManager. If the authentication fails, users are automatically directed to the login page of DeviceManager.
Translation
Download
Updated: 2019-04-28

Document ID: EDOC1000122524

Views: 10407

Downloads: 86

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next