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

eSight V300R010C00SPC200, 300, and 500 Self-Service Integration Guide 11

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).
System Networking

System Networking

Networking Scenario 1: Integration Between eSight and an AAA Server

When eSight is independently deployed and not integrated with other application systems, eSight authenticates and authorizes login users using LDAP or RADIUS.

Figure 1-6 Integration between eSight and an AAA server

Networking Scenario 2: Integration Between eSight and a Third-Party System Without Enabling SSO

When eSight and a third-party system are both independently deployed and SSO is not enabled, they use their own account management functions to authenticate and authorize login users.

eSight can use the local database or AAA server to authenticate login users.

The third-party system uses HTTP, FTP, and SNMP open interfaces to integrate eSight data. eSight then performs local authentication on protocol connections.

Figure 1-7 Integration between eSight and a third-party system without enabling SSO

Networking Scenario 3: Integration Between eSight and a Third-Party System with eSight Serving as an SSO Server

When eSight is integrated with a third-party system and SSO is enabled, eSight serves as an SSO server and the third-party system serves as an SSO client. eSight performs centralized authentication and authorization on login users.

eSight can use the local database or AAA server to authenticate login users.

The third-party system uses HTTP, FTP, and SNMP open interfaces to integrate eSight data. eSight then performs local authentication through protocol connections.

Figure 1-8 Integration between eSight and a third-party system with eSight serving as an SSO server

Networking Scenario 4: Integration Between eSight and a Third-Party System with eSight Serving as an SSO Client

When eSight is integrated and deployed with a third-party system and SSO is enabled, eSight serves as an SSO client and the third-party system serves as an SSO server. The third-party system performs centralized authentication and authorization on login users. eSight supports expansion and secondary development, and uses the SSO client toolkit released by the third-party system to provide the SSO function.

The third-party system can use the local database or AAA server to authenticate login users. eSight cannot authenticate login users authenticated by the third-party system.

The third-party system uses HTTP, FTP, and SNMP open interfaces to integrate eSight data. eSight then performs local authentication on protocol connections.

Figure 1-9 Integration between eSight and a third-party system with eSight serving as an SSO client

Download
Updated: 2019-12-13

Document ID: EDOC1100044386

Views: 21683

Downloads: 93

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next