Jump to content Japan - English

Software(Japanese)  >  Security(Japanese)

IceWall software

FAQ 2. Product Specifications
»

IceWall SSO

What Is IceWall SSO?
» What is Single Sign-On?
» What is IceWall SSO?
» Benefits
» Basic Features
Product Specifics
» Basic Architecture Diagram
» Operating Environment
» Reference Price
» Options
» FAQ
» Case Studies
» White papers
» Online Demo
» Support
» Implementation Services
» Contact Us
Related Products
» IceWall Federation
» IceWall Remote Configuration Manager

IceWall’s Office 365cloud Federation
Contact Us

2-1 Product Specifications

2-1-1  Is it possible for IceWall SSO to work with other applications or add their own features for each system?
2-1-2  How much good class is needed for Model of the server?
2-1-3  What are some of the types of supported browsers?
2-1-4  What are the supported databases in the operating environment of IceWall SSO?
2-1-5  Is there a limitation on the back-end Web server to connect to IceWall SSO
2-1-6  introducing IceWall SSO?
What are the Considerations while transitioning from the existing network configuration to the configuration via IceWall SSO?
2-1-7  Is there any limitations on the characters that are used in user ID?
2-1-8  Is URL translation possible for Japanese URL?
2-1-9  What are the management tools of IceWall SSO?
2-1-10  Is it possible to make a HTTP1.1 Connection between IceWall SSO and back-end Web server?
2-1-11  Is it possible to do encrypted communication with IceWall SSO?
2-1-12  Is IPv6 supported? Also are there any limitations?
2-1-13  How is a session managed by IceWall SSO?
2-1-14  How does IceWall SSO responds to the data of a large file size?

1.Technology

» 1-1 Authentication authorization
» 1-2 Connection to the back-end
» 1-3 Other

2.Specifications

» 2-1 Product Specifications

3.Sales

» 3-1 Track Record
» 3-2 Other

» FAQ Top page

Q.2-1-1 

Is it possible for IceWall SSO to work with other applications or add their own features for each system?

A. IceWall SSO allows you to extend the forwarders and authentication module functionality by making use of API.

For example, it is possible to integrate your own certification program or security product with IceWall SSO.
» Top of page

Q.2-1-2 

How much good class is needed for Model of the server?

A. Servers recommended for IceWall SSO 10.0 or later are as follows.

<Linux-version/Windows-version> - HPE ProLiant or equivalent Compatible computers

<HP-UX-version> - HPE Integrity server (Itanium)

In addition, which class of the server is good depends on the requirements of the system and lineup of server products, please contact us for details

» Contact us
» Top of page

Q.2-1-3 

What are some of the types of supported browsers?

A. Please see the following URL for the latest recommended operating environment of IceWall SSO.

» IceWall SSO operating environment
» Top of page

Q.2-1-4 

What are the supported databases in the operating environment of the IceWall SSO?

A. Please see the following URL for the recommended operating environment of latest.

» IceWall SSO operating environment
» Top of page

Q.2-1-5 

Is there a limitation on the back-end Web server to connect to IceWall SSO

A. Basically if application is not the one performing session management using Cookie via HTTP communication or the application is not performing session management due to original authentication not implemented, we can connect the application without problems.

For different types of applications that perform their own communication with applet and own client, there are scenarios when you need to investigate the connection, and there is the possibility that some functional restriction occurs.
» Top of page

Q.2-1-6 

introducing IceWall SSO?
What are the Considerations while transitioning from the existing network configuration to the configuration via IceWall SSO?

A. Upon introduction there are Considerations:
  1. Considerations related to Network configuration
    There is no point in particular to Consider. However if you use IceWall SSO as single sign-on solution of the reverse proxy type, then to relay access from the client then it is recommended that you move back-end Web server to a network segment with high degree of security.

  2. Considerations related to Existing system
    The introduction of the IceWall SSO, it depends on your environment , but basically you do not need to take any further action with respect to an existing Web server.

  3. Considerations related to URL
    If you have installed the IceWall SSO, URL that is accessed by the end user will change if you do not want to use the original URL corresponding function.
» Top of page

Q.2-1-7 

Is there any limitations on the characters that are used in user ID?

A. For user ID characters to be used apart from non-alphanumeric are special characters :
! % $ & @ _ - .
Blank characters are not supported.
In addition, "." (Period) can not be used at the end of the user ID.
The operation is not guarantee when using special characters other than these.
» Top of page

Q.2-1-8 

Is URL translation possible for URLs with double-byte character?

A. URL conversion is done even if the double-byte character is included as part of the URL.
In the case of performing the keyword conversion for the language, please describe to match the character code of the content in the configuration file.
» Top of page

Q.2-1-9 

What are the management tools of IceWall SSO?

A. You may include the following IceWall SSO management tools.
  • IceWall Remote Configuration Manager (Ver10.0 managed limited version number ) (up to four sets ) .
    Five or more sets or product support is paid option.
    IceWall SSO environment as well as the UNIX server and Linux server that is located in and around it can be readily accessible from the management graphical screen for changes in configuration.

    Please see the URL below for more information.
    » IceWall Remote Configuration Manager

  • (Available in Ver.10.0) Performance Monitor tool
    You can operate on the authentication server and IceWall server , which facilitates the performance analysis of IceWall SSO.
» Top of page

Q.2-1-10 

Is it possible to make a HTTP1.1 Connection between IceWall SSO and back-end Web server?

A. It is impossible. Communication between Back-end Web server and the IceWall server is restricted to using HTTP1.0.

However, the connection is possible between IceWall server and the browser using HTTP1.1.
» Top of page

Q.2-1-11 

Is it possible to do encrypted communication with IceWall SSO?

A. It is possible to perform SSL communication between back-end Web server and IceWall server by using an option in IceWall SSO.

The SSL communication IceWall between the client and server is supported by the standard.
» Top of page

Q.2-1-12 

Is IPv6 supported? Also are there any limitations?

A. IceWall SSO supports IPv6 from Ver.10.0.
» Top of page

Q.2-1-13 

How is a session managed by IceWall SSO?

A. Basically the session management is performed with session ID using Cookie.
IceWall SSO will issue a session ID Cookie for the user if the user access using the correct user ID/password.
It performs both access control as well as the authentication confirmation of user by the session ID.

It embeds session ID in a part of the path of the URL for browsers that do not supports Cookie.
Session ID will be erased if the user is performing the log out.
» Top of page

Q.2-1-14 

How does IceWall SSO responds to the data of a large file size ?

A. Not requires any special configuration. In fact forwarder handles both small size content as well as any major content even without particular distinction. However sizing IceWall server will be affected if the data size or traffic on network line is large. Further, improvement in performance is possible by adjusting the following values.
  • Adjustment of the buffer size of forwarders
  • Not implementing buffering for large files
» Top of page
Printable version
Privacy statement Using this site means you accept its terms  
Please note: all of the links on this page navigate you to pages in Japanese.