-
Getting Started with NetScaler
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
-
Web proxy support for outbound calls to IDP or third party endpoints
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud™
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
Troubleshoot authentication, authorization and auditing issues
-
Configure EULA as an authentication factor in NetScaler nFactor system
-
Configure periodic Endpoint Analysis scan as a factor in nFactor authentication
-
Configure post-authentication Endpoint Analysis scan as a factor in NetScaler nFactor authentication
-
Configure pre-authentication Endpoint Analysis scan as a factor in nFactor authentication
-
Configure pre-auth and post-auth EPA scan as a factor in nFactor authentication
-
Configure prefill user name from certificate in NetScaler nFactor authentication
-
Configure protected user as an authentication factor in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Source IP address whitelisting for GSLB communication channels
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Support for hybrid Post Quantum cryptography on the frontend
-
-
Create a certificate signing request and use SSL certificates on a NetScaler appliance
-
Configure SSL acceleration with HTTP on the front end and SSL on the back end
-
Export certificates used on a NetScaler appliance as PFX file
-
Configure SSL monitoring when client authentication is enabled on the back-end service
-
Configure SSL action to forward client traffic if a cipher is not supported on the ADC
-
Configure synchronization of files in a high availability setup
-
-
Appendix A: Sample migration of the SSL configuration after upgrade
-
Appendix B: Default front-end and back-end SSL profile settings
-
Migrate the SSL configuration to the enhanced SSL profile
-
-
-
Authentication and authorization for System Users
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Migrate the SSL configuration to the enhanced SSL profile
Note:
The terms “default” and “enhanced” are used interchangeably for the enhanced SSL profile.
A typical deployment has hundreds of virtual servers, services, and other SSL entities configured. Each entity might have its own SSL settings. Adding or changing a setting on all the entities can be a cumbersome process. To address this need and simplify the configuration process, you can use SSL profiles and attach them to different entities.
An SSL profile is a collection of SSL parameter settings for SSL entities, such as virtual servers, services (including internal services), and service groups. It offers ease of configuration and flexibility because you are not limited to configuring only one set of global parameters. There are two types of profiles:
- Front-end profile: Applies to the entities that receive requests from a client.
- Back-end profile: Applies to entities that send client requests to the back-end server.
Problem statement
When you enable the default profile, the inbuilt default SSL profiles are automatically bound to all the front-end and back-end SSL entities. The profile comes with some default settings and when you enable the default profile, your custom settings are lost. Manually fixing a large configuration can be tedious, time-consuming, and error prone. Therefore, customers are hesitant to migrate to the default profile.
Solution
From release 14.1 build 21.x, you can run a script from the NetScaler GUI that parses your configuration and creates custom profiles based on your existing settings. The script checks the configuration of your SSL entities and creates profiles for the same settings. Then, it sets the applicable profile for each SSL entity.
Perform the following steps to migrate the SSL configuration:
- Save the configuration.
- Run the script.
- Review the output file.
- Enable the default profile.
- Batch the file.
Important
Save the configuration before running the script. At the NetScaler CLI, type:
save config. Also, ensure that the default profile is enabled before you batch the file. For a large configuration, running the script can take up to 30 minutes.
To migrate the SSL configuration by using the NetScaler GUI
- Navigate to System > Diagnostics. Under Maintenance, click Save configuration.
- Navigate to Traffic Management > SSL > Tools > SSL Profile Converter.
- Click Run SSL Profile Conversion.
- Click View File to review the output file. Click Download File to download the output file and review offline.
- Go back to the SSL page. Under Settings, click Change advanced SSL settings.
- In the Change Advanced SSL settings page, select Enable Default Profile.
- Navigate to System > Diagnostics. Under Utilities, click Batch configuration.
- Provide the File Path and click Run.
Result
When you run this script, it scans the existing NetScaler configuration file.
Output file location when using admin partitions and running the script from CLI: /nsconfig/partitions/<partition_name>/sslprofile_cmds.txt.
Output file location when using the default partition and running the script from CLI or GUI: /nsconfig/sslprofile_cmds.txt.
This file contains all the enhanced SSL profile commands corresponding to the existing configuration. You need to review the file and then batch it.
The custom profiles are created with the required settings based on your configuration. The applicable profile is bound to the various front-end and back-end SSL entities.
Your SSL entities now have the same settings as before the default profile was enabled. The difference is that these settings are now part of the SSL default profile. To change the settings on multiple SSL entities, you only have to modify the associated profile. The settings are applied to all the SSL entities that the profile is attached to.
To migrate the SSL configuration by using the NetScaler CLI
You can also run the script from the CLI. At the command prompt, type:
save config
convert SSL defaultprofile
<!--NeedCopy-->
The output folders are specified in the Results section. You must review the file, enable the default profile, and then batch the file.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.