server task virtualhost create
Creates a virtual host junction.
Requires authentication (administrator ID and password) to use this command.
Syntax
- For local junctions:
- server task
instance_name-webseald-host_namevirtualhost create–ttype–ddir–vvirtual_host_name[options]vhost_label - For non-local junctions:
- server task
instance_name-webseald-host_namevirtualhost create–ttype–hhost_name[options]vhost_label
Options
–ddir- Specifies the local directory for a local virtual host junction.
This option is required for
localtcpandlocalssljunction types. –hhost_name- Specifies the DNS host name or IP address of the target server. This option is valid only for
non-local junctions; local junctions do not need a host name. Valid values for
host_nameinclude any valid IP host name. For example:www.example.com –ttype- Specifies the type of virtual host junction. This option is required and must be one of the
following types:
tcptcpproxysslsslproxylocaltcplocalssl
–vvirtual_host_name[:port]-
WebSEAL selects a virtual host junction to process a request if the HTTP Host header of the request matches:
- The virtual host name by the -v option and
- The port number that is specified by the -v option.
The
–voption is also used to specify the value of the Host header of the request sent to the server.The port number is required if the virtual host uses a non-standard port for the protocol. Standard port for TCP is 80; standard port for SSL is 443.
If
–vis not specified fortcp,ssl,tcpproxy, andsslproxytype junctions, the junction is selected from the information that is contained in the–hhost_nameand–pportoptions.The
–voption is required forlocaltcpandlocalssltype junctions instance_name-webseald-host_name- Specifies the full server name of the installed WebSEAL server instance. You must specify this
full server name in the exact format as displayed in the output of the server
list command.
The
instance_namespecifies the configured name of the WebSEAL server instance. Thewebsealddesignation indicates that the WebSEAL service performs the command task. Thehost_nameis the name of the physical computer where the WebSEAL server is installed.For example, the configured name of a single WebSEAL server instance is
default. The host computer name where the WebSEAL server is installed isabc.ibm.com. Then, the full WebSEAL server name isdefault-webseald-abc.ibm.com.If an additional WebSEAL server instance is configured and named
web2, the full WebSEAL server name isweb2-webseald-abc.ibm.com. options- Specifies the options that you can use with the server task virtualhost
create command. (Optional) These options include:
–A- Enables a virtual host junction to support the lightweight third-party authentication mechanism
(LTPA). This option requires the
–Fand–Zoptions. The–A,–F, and–Zoptions all must be used together.This option is valid for all junction types except
localtcpandlocalssl. –2- You can use this option with the
–Aoption to specify that LTPA version 2 cookies (LtpaToken2) are used. The–Aoption without the–2option specifies that LTPA version 1 cookies (LtpaToken) are used. –bBA_value- Defines how the WebSEAL server passes client identity information in HTTP basic authentication
(BA) headers to the virtual host, which is one of the following values:
filterignoresupplygso
This option is valid for all junction types except
localtcpandlocalssl. The default value isfilter. –B- Indicates that WebSEAL uses the BA header information to authenticate to the virtual host and to
provide mutual authentication over SSL. This option requires the
–Uand–Woptions.This option is valid only with junctions that were created with the type of
sslorsslproxy. –cheader_type- Inserts the Security Access Manager client identity
in HTTP headers across the virtual host junction. The
header_typeargument can include any combination of the listed Security Access Manager HTTP header types:{iv_user|iv_user-l}iv_groupsiv_credsall
The header types must be comma-separated, and cannot have a space between the types. For example:
-c iv_user,iv_groupsSpecifying
–callis the same as specifying–civ_user,iv_groups,iv_creds.This option is valid for all junction types except
localtcpandlocalssl. –C- Supports mutual authentication by enabling the front-end WebSEAL server to pass its identity
information to the back-end WebSEAL server. The front-end WebSEAL server passes information in a
Basic Authentication (BA) header. Additionally, the
–Coption enables the single sign-on functionality that is provided by the–coption.This option is valid only with junctions that were created with the type of
sslorsslproxy. –D"dn"- Specifies the distinguished name of the server certificate. This value, matched with the actual
certificate DN, enhances authentication and provides mutual authentication over SSL. For example,
the certificate for
www.example.commight have a DN of"CN=WWW.EXAMPLE.COM,OU=Software,O=example.com\, Inc,L=Austin, ST=Texas,C=US"This option is valid only with junctions that were created with the type of
sslorsslproxy. –eencoding_type- Specifies the encoding to use when HTTP headers is generated for virtual host junctions. This
encoding applies to headers that are generated with both the
–cjunction option and tag-value. Possible values for encoding are as follows:- utf8_bin
- WebSEAL sends the headers in UTF-8.
- utf8_uri
- WebSEAL sends the headers in UTF-8 but URI also encodes them. This behavior is the default behavior.
- lcp_bin
- WebSEAL sends the headers in the local code page of the WebSEAL server.
- lcp_uri
- WebSEAL sends the headers in the local code page of the WebSEAL server, but URI also encodes them.
This option is valid for all junction types except
localtcpandlocalssl. –f- Forces the replacement (overwrite) of an existing virtual host junction.
This option is used for junctions that were created with any junction type.
–F"keyfile"- Specifies the location of the key file that is used to encrypt LTPA cookie data.
The
–Foption requires–Aand–Zoptions. The–A,–F, and–Zoptions all must be used together.This option is valid for all junction types except
localtcpandlocalssl. –gvhost_label- The
–goption causes a second more virtual host junction to share a protected object space as the initial virtual host junction.This option is appropriate for junction pairs only (two junctions by using complementary protocols). The option does not support the association of more than two junctions.
–Hhost_name- Specifies the DNS host name or IP address of the proxy server. The
–Poption also supports proxy server junctions. Valid values forhost_nameinclude any valid IP host name. For example:
This option is valid only with junctions that were created with the type ofproxy.www.example.comtcpproxyorsslproxy. –i- Indicates that the WebSEAL junction does not treat URLs as case-sensitive. To correctly
authorize requests for junctions that are not case-sensitive, WebSEAL does the authorization check
on a lowercase version of the URL. For example, a web server that is running on a Windows operating system treats requests for
INDEX.HTMandindex.htmas requests for the same file.Junctions to such a web server must be created with the–ior–woption. ACLs or POPs that are attached to objects beneath the junction point must use the lowercase object name. An ACL attached to/junction/index.htmapplies to all the following requests if the–ior–woption is used:/junction/INDEX.HTM/junction/index.htm/junction/InDeX.HtM
This option is valid for all junction except for the type of
localtcpandlocalssl. Local junctions are not case-sensitive only on Win32 platforms; all other platforms are case-sensitive. –k- Sends WebSEAL session cookies to the back-end virtual host. By default, cookies are removed from
requests that are sent to the server.
This option is valid for all junction types except
localtcpandlocalssl. –K"key_label"- Specifies the key label of the client-side certificate that WebSEAL must present to the server.
Use of this option allows the virtual host to authenticate the WebSEAL server by using client
certificates.
This option is valid only with junctions that were created with the type of
sslandsslproxy. –lpercent- Defines the soft limit for consumption of worker threads.
This option is valid for all junction types except
localtcpandlocalssl. –Lpercent- Defines the hard limit for consumption of worker threads.
This option is valid for all junction types except
localtcpandlocalssl. –pport- Specifies the TCP port of the third-party server. The default value is
80for TCP junctions and443for SSL junctions.This option is valid for all junction types except
localtcpandlocalssl. –Pport- Specifies the TCP port number for the HTTP proxy server. The
–Poption is required when the–Hoption is used.This option is valid only with junctions that were created with the type of
tcpproxyorsslproxy. –q–S- Specifies the relative path for the query_contents script. By default,
Security Access Manager looks for the
query_contents script in the /cgi_bin directory. If this
directory is different or the query_contents file name is renamed, this option
indicates to WebSEAL the new URL to the file. Required for Windows virtual hosts.
This option is valid for all junction types except
localtcpandlocalssl. –r- Inserts the incoming IP address into the HTTP header across the junction.
This option is valid for all junction types except
localtcpandlocalssl. –R- Allows the request to proceed but provides the rule failure reason to the junction in an HTTP
header. If the
–Roption is not used and a rule failure occurs, WebSEAL does not allow the request to proceed.This option is valid for all junction types except
localtcpandlocalssl. –s- Indicates that the virtual host junction support stateful applications. By default, virtual host
junctions are not stateful.
This option is valid for all junction types except
localtcpandlocalssl. –S- Indicates the location of the forms single sign-on configuration file.
This option is valid for all junction types except
localtcpandlocalssl. –T{resource|resource_group}- Specifies the name of the GSO resource or resource group. This option is required only when the
–bgsooption is used.This option is valid for all junction types except
localtcpandlocalssl. –uuuid- Specifies the Universally Unique Identifier (UUID) of a server that is connected to WebSEAL by
using a stateful virtual host junction (
–soption).This option is valid for all junction types except
localtcpandlocalssl. –U"user_name"- Specifies the WebSEAL server user name. This option requires the
–Band–Woptions. WebSEAL uses the BA header information to authenticate to the virtual host and to provide mutual authentication over SSL.This option is valid only with junctions that were created with the type of
sslorsslproxy. –w- Indicates Microsoft
Windows 32 bit (Win32) file system support. This option
provides all the functionality that is provided by the
–ijunction option. The option disallows requests that contain file names that might be interpreted as Win32 file name aliases.This option is valid for all junction types except
localtcpandlocalssl. Local junctions prohibit URLs that contain Win32 file name aliases on Win32 but allow such URLs on other platforms. –W"password"- Specifies the WebSEAL server password. This option requires the
–Band–Uoptions. WebSEAL uses the BA header information to authenticate to the virtual host and to provide mutual authentication over SSL.This option is valid only with junctions that were created with the type of
sslorsslproxy. –Y- Enables the Federation Runtime single sign-on
(SSO) for the junction. Note: Before you use this option, you must first configure the WebSEAL configuration file to support the Federation Runtime single sign-on over junctions.
–zreplica_set- Specifies the replica set, as follows:
- For SMS environments:
- Sessions on the virtual host junction are managed under the specified replica set. Used to group or separate login sessions among multiple virtual hosts.
- For non-SMS environments:
- Sessions on the virtual host junction are managed under the specified replica set. Controls the
partitioning of the WebSEAL session cache. The virtual host can be part of the same replica set as
any standard junction that is assigned to that same replica set. Standard junctions are assigned to
replica sets through the
standard-junction-replica-setentry of the[session]stanza.
–Zkeyfile_pwd- Specifies the password of the key file that is used to encrypt LTPA cookie data. This option
requires the
–Aand–Foptions. The–A,–F, and–Zoptions all must be used together.This option is valid for all junction types except
localtcpandlocalssl.
vhost_label- Specifies the label name of the virtual host junction.
Authorization
Users and groups that require access to this command must be given the s
(server administration) permission in the ACL that governs the
/WebSEAL/
object. For example, the sec_master administrative user is given this
permission by default.host_name-instance_name/@vhost_label
Return codes
- 0
- The command completed successfully. For WebSEAL server task commands, the
return code is
0when the command is sent to the WebSEAL server without errors. However, even after the command was successfully sent, the WebSEAL server might not be able to successfully complete the command. The WebSEAL server returns an error message. - 1
- The command failed. See "Error messages" in the IBM Knowledge Center. This reference provides a list of the Security Access Manager error messages by decimal or hexadecimal codes.
For more information about gathering statistics, see the Troubleshooting topics in the IBM Knowledge Center.
Example
vhost-xy-https label. This junction serves the virtual host
x.y.com on the junctioned server cruz1.ibm.com. WebSEAL responds
to the Host: x.y.com header in SSL (HTTPS) requests by forwarding the requests
across this virtual host junction:
pdadmin> server task default-webseald-abc.ibm.com virtualhost create \
-t ssl -h cruz1.ibm.com -v x.y.com vhost-xy-https